Apparatus for receiving broadcast signal and method for receiving broadcast signal

ABSTRACT

An apparatus for receiving a broadcast signal includes a tuner configured to receive a broadcast signal, the broadcast signal including service components of a broadcast service, service signaling information signaling the broadcast service and a service list table including information for bootstrapping the service signaling information; a hardware processor configured to parse the broadcast signal and obtain the service list table, the service signaling information and the service components of the broadcast service, wherein the service signaling information includes first session description data and second session description data, wherein the first session description data includes IP/UDP information identifying a Real-Time Object Delivery over Unidirectional Transport (ROUTE) session in the broadcast signal, and the second session description data for the identified ROUTE session includes Transport Session Identifiers (TSIs) for identifying Layered Coding Transport (LCT) channels that carry the service components delivered through the identified ROUTE session.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a Continuation of co-pending U.S. patent applicationSer. No. 14/909,882 filed on Feb. 3, 2016, which is the National Phaseof PCT International Application No. PCT/KR2015/012976 filed on Dec. 1,2015, which claims the benefit under 35 U.S.C. § 119(e) to U.S.Provisional Application No. 62/090,351 filed on Dec. 10, 2014, all ofwhich are hereby expressly incorporated by reference into the presentapplication.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to an apparatus for transmitting abroadcast signal, an apparatus for receiving a broadcast signal andmethods for transmitting and receiving a broadcast signal.

Discussion of the Related Art

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals arebeing developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

SUMMARY OF THE INVENTION

That is, a digital broadcast system can provide HD (high definition)images, multichannel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

The present invention provides a system capable of effectivelysupporting future broadcast services in an environment supporting futurehybrid broadcasting using terrestrial broadcast networks and theInternet and related signaling methods.

The present invention can control quality of service (QoS) with respectto services or service components by processing data on the basis ofservice characteristics, thereby providing various broadcast services.

The present invention can achieve transmission flexibility bytransmitting various broadcast services through the same radio frequency(RF) signal bandwidth.

The present invention can provide methods and apparatuses fortransmitting and receiving broadcast signals, which enable digitalbroadcast signals to be received without error even when a mobilereception device is used or even in an indoor environment.

The present invention can effectively support future broadcast servicesin an environment supporting future hybrid broadcasting usingterrestrial broadcast networks and the Internet.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention;

FIG. 2 illustrates a relation between an SLT and service layer signaling(SLS) according to an embodiment of the present invention;

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention;

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention;

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention;

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention;

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention;

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention;

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention;

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention;

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention;

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention;

FIG. 13 illustrates an example of adaptation modes in Internet Protocol(IP) header compression according to an embodiment of the presentinvention (transmitting side);

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention;

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention;

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention;

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides);

FIG. 18 is a block diagram illustrating a configuration of a broadcastsignal transmission apparatus for future broadcast services according toan embodiment of the present invention;

FIG. 19 is a block diagram illustrating a bit interleaved coding &modulation (BICM) block according to an embodiment of the presentinvention;

FIG. 20 is a block diagram illustrating a BICM block according toanother embodiment of the present invention;

FIG. 21 illustrates a bit interleaving process of physical layersignaling (PLS) according to an embodiment of the present invention;

FIG. 22 is a block diagram illustrating a configuration of a broadcastsignal reception apparatus for future broadcast services according to anembodiment of the present invention;

FIG. 23 illustrates a signaling hierarchy structure of a frame accordingto an embodiment of the present invention;

FIG. 24 is a table illustrating PLS1 data according to an embodiment ofthe present invention;

FIG. 25 is a table illustrating PLS2 data according to an embodiment ofthe present invention;

FIG. 26 is a table illustrating PLS2 data according to anotherembodiment of the present invention;

FIG. 27 illustrates a logical structure of a frame according to anembodiment of the present invention;

FIG. 28 illustrates PLS mapping according to an embodiment of thepresent invention;

FIG. 29 illustrates time interleaving according to an embodiment of thepresent invention;

FIG. 30 illustrates a basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention;

FIG. 31 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention;

FIG. 32 is a block diagram illustrating an interleaving addressgenerator including a main pseudo-random binary sequence (PRBS)generator and a sub-PRBS generator according to each FFT mode accordingto an embodiment of the present invention;

FIG. 33 illustrates a main PRBS used for all FFT modes according to anembodiment of the present invention;

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleavingaddress for frequency interleaving according to an embodiment of thepresent invention;

FIG. 35 illustrates a write operation of a time interleaver according toan embodiment of the present invention;

FIG. 36 is a table illustrating an interleaving type applied accordingto the number of PLPs;

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver;

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver;

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver;

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver;

FIG. 41 is a block diagram illustrating a configuration of a broadcastsystem according to an embodiment of the present invention;

FIG. 42 illustrates a configuration of signaling data according to afirst embodiment of the present invention;

FIG. 43 illustrates a service according to the first embodiment of thepresent invention;

FIG. 44 illustrates an SMT according to the first embodiment of thepresent invention;

FIG. 45 illustrates a configuration of signaling data according to asecond embodiment of the present invention;

FIG. 46 illustrates USD according to the second embodiment of thepresent invention;

FIG. 47 illustrates a service according to the second embodiment of thepresent invention;

FIG. 48 illustrates a configuration of signaling data according to athird embodiment of the present invention;

FIG. 49 illustrates USD according to the third embodiment of the presentinvention;

FIG. 50 illustrates a service according to the third embodiment of thepresent invention;

FIG. 51 illustrates a configuration of signaling data according to afourth embodiment of the present invention;

FIG. 52 illustrates a service according to the fourth embodiment of thepresent invention;

FIG. 53 illustrates a configuration of signaling data according to afifth embodiment of the present invention;

FIG. 54 illustrates a service according to the fifth embodiment of thepresent invention;

FIG. 55 illustrates a configuration of signaling data according to asixth embodiment of the present invention;

FIG. 56 illustrates effects of signaling according to the first to sixthembodiments of the present invention;

FIG. 57 is a flowchart illustrating a broadcast transmission methodaccording to an embodiment of the present invention;

FIG. 58 is a flowchart illustrating a broadcast reception methodaccording to an embodiment of the present invention;

FIG. 59 illustrates a configuration of signaling data according to aseventh embodiment of the present invention;

FIG. 60 illustrates a USD according to the seventh embodiment of thepresent invention;

FIG. 61 illustrates an ATSC SDP and/or an LSID according to the seventhembodiment of the present invention;

FIG. 62 illustrates service layer signaling according to the seventhembodiment of the present invention;

FIG. 63 illustrates a method of reducing a signaling size according toan eighth embodiment of the present invention;

FIG. 64 illustrates a USD according to a ninth embodiment of the presentinvention;

FIG. 65 illustrates service layer signaling according to a ninthembodiment of the present invention;

FIG. 66 illustrates a configuration of signaling data according to atenth embodiment of the present invention;

FIG. 67 illustrates a configuration of signaling data according to thetenth embodiment of the present invention;

FIG. 68 illustrates an example of transmission according to servicelayer signaling data transmission intervals according to the tenthembodiment of the present invention;

FIG. 69 illustrates an example of transmission according to the servicelayer signaling data transmission intervals according to the tenthembodiment of the present invention;

FIG. 70 illustrates a configuration of signaling data according to athirteenth embodiment of the present invention;

FIG. 71 illustrates an SDP according to the thirteenth embodiment of thepresent invention;

FIG. 72 illustrates service layer signaling according to the thirteenthembodiment of the present invention;

FIG. 73 illustrates service layer signaling according to the thirteenthembodiment of the present invention;

FIG. 74 illustrates a signaling structure for signaling capabilities ofa receiver for consuming broadcast services/content according to anembodiment of the present invention;

FIG. 75 illustrates a procedure through which the receiver accessesbroadcast services/content using the signaling structure according to anembodiment of the present invention;

FIG. 76 illustrates a USD which provides information about a transportsession through which data of broadcast services/content is transmittedaccording to an embodiment of the present invention;

FIG. 77 illustrates a procedure through which the receiver accessesbroadcast services/content using a signaling structure according to anembodiment of the present invention;

FIG. 78 is a flowchart illustrating a method for generating andprocessing a broadcast signal according to an embodiment of the presentinvention;

FIG. 79 is a block diagram of a broadcast system according to anembodiment of the present invention;

FIG. 80 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention;

FIG. 81 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention;

FIG. 82 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention;

FIG. 83 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention;

FIG. 84 is a flowchart illustrating a method for transmitting abroadcast signal according to an embodiment of the present invention;and

FIG. 85 is a block diagram of an apparatus for transmitting a broadcastsignal according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although the terms used in the present invention are selected fromgenerally known and used terms, some of the terms mentioned in thedescription of the present invention have been selected by the applicantat his or her discretion, the detailed meanings of which are describedin relevant parts of the description herein. Furthermore, it is requiredthat the present invention is understood, not simply by the actual termsused but by the meanings of each term lying within.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, anultra high definition television (UHDTV) service, etc. The presentinvention may process broadcast signals for the future broadcastservices through non-MIMO (Multiple Input Multiple Output) or MIMOaccording to one embodiment. A non-MIMO scheme according to anembodiment of the present invention may include a MISO (Multiple InputSingle Output) scheme, a SISO (Single Input Single Output) scheme, etc.

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention.

Two schemes may be used in broadcast service delivery through abroadcast network.

In a first scheme, media processing units (MPUs) are transmitted usingan MMT protocol (MMTP) based on MPEG media transport (MMT). In a secondscheme, dynamic adaptive streaming over HTTP (DASH) segments may betransmitted using real time object delivery over unidirectionaltransport (ROUTE) based on MPEG DASH.

Non-timed content including NRT media, EPG data, and other files isdelivered with ROUTE. Signaling may be delivered over MMTP and/or ROUTE,while bootstrap signaling information is provided by the means of theService List Table (SLT).

In hybrid service delivery, MPEG DASH over HTTP/TCP/IP is used on thebroadband side. Media files in ISO Base Media File Format (BMFF) areused as the delivery, media encapsulation and synchronization format forboth broadcast and broadband delivery. Here, hybrid service delivery mayrefer to a case in which one or more program elements are deliveredthrough a broadband path.

Services are delivered using three functional layers. These are thephysical layer, the delivery layer and the service management layer. Thephysical layer provides the mechanism by which signaling, serviceannouncement and IP packet streams are transported over the broadcastphysical layer and/or broadband physical layer. The delivery layerprovides object and object flow transport functionality. It is enabledby the MMTP or the ROUTE protocol, operating on a User Datagram Protocol(UDP)/IP multicast over the broadcast physical layer, and enabled by theHTTP protocol on a TCP/IP unicast over the broadband physical layer. Theservice management layer enables any type of service, such as linear TVor HTML5 application service, to be carried by the underlying deliveryand physical layers.

In this figure, a protocol stack part on a broadcast side may be dividedinto a part transmitted through the SLT and the MMTP, and a parttransmitted through ROUTE.

The SLT may be encapsulated through UDP and IP layers. Here, the SLTwill be described below. The MMTP may transmit data formatted in an MPUformat defined in MMT, and signaling information according to the MMTP.The data may be encapsulated through the UDP and IP layers. ROUTE maytransmit data formatted in a DASH segment form, signaling information,and non-timed data such as NRT data, etc. The data may be encapsulatedthrough the UDP and IP layers. According to a given embodiment, some orall processing according to the UDP and IP layers may be omitted. Here,the illustrated signaling information may be signaling informationrelated to a service.

The part transmitted through the SLT and the MMTP and the parttransmitted through ROUTE may be processed in the UDP and IP layers, andthen encapsulated again in a data link layer. The link layer will bedescribed below. Broadcast data processed in the link layer may bemulticast as a broadcast signal through processes such asencoding/interleaving, etc. in the physical layer.

In this figure, a protocol stack part on a broadband side may betransmitted through HTTP as described above. Data formatted in a DASHsegment form, signaling information, NRT information, etc. may betransmitted through HTTP. Here, the illustrated signaling informationmay be signaling information related to a service. The data may beprocessed through the TCP layer and the IP layer, and then encapsulatedinto the link layer. According to a given embodiment, some or all of theTCP, the IP, and the link layer may be omitted. Broadband data processedthereafter may be transmitted by unicast in the broadband through aprocess for transmission in the physical layer.

Service can be a collection of media components presented to the user inaggregate; components can be of multiple media types; a Service can beeither continuous or intermittent; a Service can be Real Time orNon-Real Time; Real Time Service can consist of a sequence of TVprograms.

FIG. 2 illustrates a relation between the SLT and SLS according to anembodiment of the present invention.

Service signaling provides service discovery and descriptioninformation, and comprises two functional components: Bootstrapsignaling via the Service List Table (SLT) and the Service LayerSignaling (SLS). These represent the information which is necessary todiscover and acquire user services. The SLT enables the receiver tobuild a basic service list, and bootstrap the discovery of the SLS foreach service.

The SLT can enable very rapid acquisition of basic service information.The SLS enables the receiver to discover and access services and theircontent components. Details of the SLT and SLS will be described below.

As described in the foregoing, the SLT may be transmitted throughUDP/IP. In this instance, according to a given embodiment, datacorresponding to the SLT may be delivered through the most robust schemein this transmission.

The SLT may have access information for accessing SLS delivered by theROUTE protocol. In other words, the SLT may be bootstrapped into SLSaccording to the ROUTE protocol. The SLS is signaling informationpositioned in an upper layer of ROUTE in the above-described protocolstack, and may be delivered through ROUTE/UDP/IP. The SLS may betransmitted through one of LCT sessions included in a ROUTE session. Itis possible to access a service component corresponding to a desiredservice using the SLS.

In addition, the SLT may have access information for accessing an MMTsignaling component delivered by MMTP. In other words, the SLT may bebootstrapped into SLS according to the MMTP. The SLS may be delivered byan MMTP signaling message defined in MMT. It is possible to access astreaming service component (MPU) corresponding to a desired serviceusing the SLS. As described in the foregoing, in the present invention,an NRT service component is delivered through the ROUTE protocol, andthe SLS according to the MMTP may include information for accessing theROUTE protocol. In broadband delivery, the SLS is carried overHTTP(S)/TCP/IP.

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention.

First, a description will be given of a relation among respectivelogical entities of service management, delivery, and a physical layer.

Services may be signaled as being one of two basic types. First type isa linear audio/video or audio-only service that may have an app-basedenhancement. Second type is a service whose presentation and compositionis controlled by a downloaded application that is executed uponacquisition of the service. The latter can be called an “app-based”service.

The rules regarding presence of ROUTE/LCT sessions and/or MMTP sessionsfor carrying the content components of a service may be as follows.

For broadcast delivery of a linear service without app-basedenhancement, the service's content components can be carried by either(but not both): (1) one or more ROUTE/LCT sessions, or (2) one or moreMMTP sessions.

For broadcast delivery of a linear service with app-based enhancement,the service's content components can be carried by: (1) one or moreROUTE/LCT sessions, and (2) zero or more MMTP sessions.

In certain embodiments, use of both MMTP and ROUTE for streaming mediacomponents in the same service may not be allowed.

For broadcast delivery of an app-based service, the service's contentcomponents can be carried by one or more ROUTE/LCT sessions.

Each ROUTE session comprises one or more LCT sessions which carry as awhole, or in part, the content components that make up the service. Instreaming services delivery, an LCT session may carry an individualcomponent of a user service such as an audio, video or closed captionstream. Streaming media is formatted as DASH Segments.

Each MMTP session comprises one or more MMTP packet flows which carryMMT signaling messages or as a whole, or in part, the content component.An MMTP packet flow may carry MMT signaling messages or componentsformatted as MPUs.

For the delivery of NRT User Services or system metadata, an LCT sessioncarries file-based content items. These content files may consist ofcontinuous (time-based) or discrete (non-time-based) media components ofan NRT service, or metadata such as Service Signaling or ESG fragments.Delivery of system metadata such as service signaling or ESG fragmentsmay also be achieved through the signaling message mode of MMTP.

A broadcast stream is the abstraction for an RF channel, which isdefined in terms of a carrier frequency centered within a specifiedbandwidth. It is identified by the pair [geographic area, frequency]. Aphysical layer pipe (PLP) corresponds to a portion of the RF channel.Each PLP has certain modulation and coding parameters. It is identifiedby a PLP identifier (PLPID), which is unique within the broadcast streamit belongs to. Here, PLP can be referred to as DP (data pipe).

Each service is identified by two forms of service identifier: a compactform that is used in the SLT and is unique only within the broadcastarea; and a globally unique form that is used in the SLS and the ESG. AROUTE session is identified by a source IP address, destination IPaddress and destination port number. An LCT session (associated with theservice component(s) it carries) is identified by a transport sessionidentifier (TSI) which is unique within the scope of the parent ROUTEsession. Properties common to the LCT sessions, and certain propertiesunique to individual LCT sessions, are given in a ROUTE signalingstructure called a service-based transport session instance description(S-TSID), which is part of the service layer signaling. Each LCT sessionis carried over a single physical layer pipe. According to a givenembodiment, one LCT session may be transmitted through a plurality ofPLPs. Different LCT sessions of a ROUTE session may or may not becontained in different physical layer pipes. Here, the ROUTE session maybe delivered through a plurality of PLPs. The properties described inthe S-TSID include the TSI value and PLPID for each LCT session,descriptors for the delivery objects/files, and application layer FECparameters.

A MMTP session is identified by destination IP address and destinationport number. An MMTP packet flow (associated with the servicecomponent(s) it carries) is identified by a packet_id which is uniquewithin the scope of the parent MMTP session. Properties common to eachMMTP packet flow, and certain properties of MMTP packet flows, are givenin the SLT. Properties for each MMTP session are given by MMT signalingmessages, which may be carried within the MMTP session. Different MMTPpacket flows of a MMTP session may or may not be contained in differentphysical layer pipes. Here, the MMTP session may be delivered through aplurality of PLPs. The properties described in the MMT signalingmessages include the packet_id value and PLPID for each MMTP packetflow. Here, the MMT signaling messages may have a form defined in MMT,or have a deformed form according to embodiments to be described below.

Hereinafter, a description will be given of low level signaling (LLS).

Signaling information which is carried in the payload of IP packets witha well-known address/port dedicated to this function is referred to aslow level signaling (LLS). The IP address and the port number may bedifferently configured depending on embodiments. In one embodiment, LLScan be transported in IP packets with address 224.0.23.60 anddestination port 4937/udp. LLS may be positioned in a portion expressedby “SLT” on the above-described protocol stack. However, according to agiven embodiment, the LLS may be transmitted through a separate physicalchannel (dedicated channel) in a signal frame without being subjected toprocessing of the UDP/IP layer.

UDP/IP packets that deliver LLS data may be formatted in a form referredto as an LLS table. A first byte of each UDP/IP packet that delivers theLLS data may correspond to a start of the LLS table. The maximum lengthof any LLS table is limited by the largest IP packet that can bedelivered from the PHY layer, 65,507 bytes.

The LLS table may include an LLS table ID field that identifies a typeof the LLS table, and an LLS table version field that identifies aversion of the LLS table. According to a value indicated by the LLStable ID field, the LLS table may include the above-described SLT or arating region table (RRT). The RRT may have information about contentadvisory rating.

Hereinafter, the SLT will be described. LLS can be signaling informationwhich supports rapid channel scans and bootstrapping of serviceacquisition by the receiver, and SLT can be a table of signalinginformation which is used to build a basic service listing and providebootstrap discovery of SLS.

The function of the SLT is similar to that of the program associationtable (PAT) in MPEG-2 Systems, and the fast information channel (FIC)found in ATSC Systems. For a receiver first encountering the broadcastemission, this is the place to start. SLT supports a rapid channel scanwhich allows a receiver to build a list of all the services it canreceive, with their channel name, channel number, etc., and SLT providesbootstrap information that allows a receiver to discover the SLS foreach service. For ROUTE/DASH-delivered services, the bootstrapinformation includes the destination IP address and destination port ofthe LCT session that carries the SLS. For MMT/MPU-delivered services,the bootstrap information includes the destination IP address anddestination port of the MMTP session carrying the SLS.

The SLT supports rapid channel scans and service acquisition byincluding the following information about each service in the broadcaststream. First, the SLT can include information necessary to allow thepresentation of a service list that is meaningful to viewers and thatcan support initial service selection via channel number or up/downselection. Second, the SLT can include information necessary to locatethe service layer signaling for each service listed. That is, the SLTmay include access information related to a location at which the SLS isdelivered.

The illustrated SLT according to the present embodiment is expressed asan XML document having an SLT root element. According to a givenembodiment, the SLT may be expressed in a binary format or an XMLdocument.

The SLT root element of the SLT illustrated in the figure may include@bsid, @sltSectionVersion, @sltSectionNumber, @totalSltSectionNumbers,@language, @capabilities, InetSigLoc and/or Service. According to agiven embodiment, the SLT root element may further include @providerId.According to a given embodiment, the SLT root element may not include@language.

The service element may include @serviceId, @SLTserviceSeqNumber,@protected, @majorChannelNo, @minorChannelNo, @serviceCategory,@shortServiceName, @hidden, @slsProtocolType, BroadcastSignaling,@slsPlpId, @slsDestinationIpAddress, @slsDestinationUdpPort,@slsSourceIpAddress, @slsMajorProtocolVersion, @SlsMinorProtocolVersion,@serviceLanguage, @broadbandAccessRequired, @capabilities and/orInetSigLoc.

According to a given embodiment, an attribute or an element of the SLTmay be added/changed/deleted. Each element included in the SLT mayadditionally have a separate attribute or element, and some attribute orelements according to the present embodiment may be omitted. Here, afield which is marked with @ may correspond to an attribute, and a fieldwhich is not marked with @ may correspond to an element.

@bsid is an identifier of the whole broadcast stream. The value of BSIDmay be unique on a regional level.

@providerId can be an index of broadcaster that is using part or all ofthis broadcast stream. This is an optional attribute. When it's notpresent, it means that this broadcast stream is being used by onebroadcaster. @providerId is not illustrated in the figure.

@sltSectionVersion can be a version number of the SLT section. ThesltSectionVersion can be incremented by 1 when a change in theinformation carried within the slt occurs. When it reaches maximumvalue, it wraps around to 0.

@sltSectionNumber can be the number, counting from 1, of this section ofthe SLT. In other words, @sltSectionNumber may correspond to a sectionnumber of the SLT section. When this field is not used,@sltSectionNumber may be set to a default value of 1.

@totalSltSectionNumbers can be the total number of sections (that is,the section with the highest sltSectionNumber) of the SLT of which thissection is part. sltSectionNumber and totalSltSectionNumbers togethercan be considered to indicate “Part M of N” of one portion of the SLTwhen it is sent in fragments. In other words, when the SLT istransmitted, transmission through fragmentation may be supported. Whenthis field is not used, @totalSltSectionNumbers may be set to a defaultvalue of 1. A case in which this field is not used may correspond to acase in which the SLT is not transmitted by being fragmented.

@language can indicate primary language of the services included in thisslt instance. According to a given embodiment, a value of this field mayhave a three-character language code defined in the ISO. This field maybe omitted.

@capabilities can indicate required capabilities for decoding andmeaningfully presenting the content for all the services in this sltinstance.

InetSigLoc can provide a URL telling the receiver where it can acquireany requested type of data from external server(s) via broadband. Thiselement may include @urlType as a lower field. According to a value ofthe @urlType field, a type of a URL provided by InetSigLoc may beindicated. According to a given embodiment, when the @urlType field hasa value of 0, InetSigLoc may provide a URL of a signaling server. Whenthe @urlType field has a value of 1, InetSigLoc may provide a URL of anESG server. When the @urlType field has other values, the field may bereserved for future use.

The service field is an element having information about each service,and may correspond to a service entry. Service element fieldscorresponding to the number of services indicated by the SLT may bepresent. Hereinafter, a description will be given of a lowerattribute/element of the service field.

@serviceId can be an integer number that uniquely identify this servicewithin the scope of this broadcast area. According to a givenembodiment, a scope of @serviceId may be changed. @SLTserviceSeqNumbercan be an integer number that indicates the sequence number of the SLTservice information with service ID equal to the serviceId attributeabove. SLTserviceSeqNumber value can start at 0 for each service and canbe incremented by 1 every time any attribute in this service element ischanged. If no attribute values are changed compared to the previousService element with a particular value of ServiceID thenSLTserviceSeqNumber would not be incremented. The SLTserviceSeqNumberfield wraps back to 0 after reaching the maximum value.

@protected is flag information which may indicate whether one or morecomponents for significant reproduction of the service are in aprotected state. When set to “1” (true), that one or more componentsnecessary for meaningful presentation is protected. When set to “0”(false), this flag indicates that no components necessary for meaningfulpresentation of the service are protected. Default value is false.

@majorChannelNo is an integer number representing the “major” channelnumber of the service. An example of the field may have a range of 1 to999.

@minorChannelNo is an integer number representing the “minor” channelnumber of the service. An example of the field may have a range of 1 to999.

@serviceCategory can indicate the category of this service. This fieldmay indicate a type that varies depending on embodiments. According to agiven embodiment, when this field has values of 1, 2, and 3, the valuesmay correspond to a linear A/V service, a linear audio only service, andan app-based service, respectively. When this field has a value of 0,the value may correspond to a service of an undefined category. Whenthis field has other values except for 1, 2, and 3, the field may bereserved for future use. @shortServiceName can be a short string name ofthe Service.

@hidden can be boolean value that when present and set to “true”indicates that the service is intended for testing or proprietary use,and is not to be selected by ordinary TV receivers. The default value is“false” when not present.

@slsProtocolType can be an attribute indicating the type of protocol ofService Layer Signaling used by this service. This field may indicate atype that varies depending on embodiments. According to a givenembodiment, when this field has values of 1 and 2, protocols of SLS usedby respective corresponding services may be ROUTE and MMTP,respectively. When this field has other values except for 0, the fieldmay be reserved for future use. This field may be referred to as@slsProtocol.

BroadcastSignaling and lower attributes/elements thereof may provideinformation related to broadcast signaling. When the BroadcastSignalingelement is not present, the child element InetSigLoc of the parentservice element can be present and its attribute urlType includesURL_type 0x00 (URL to signaling server). In this case attribute urlsupports the query parameter svc=<service_id> where service_idcorresponds to the serviceId attribute for the parent service element.

Alternatively when the BroadcastSignaling element is not present, theelement InetSigLoc can be present as a child element of the slt rootelement and the attribute urlType of that InetSigLoc element includesURL_type 0x00 (URL to signaling server). In this case, attribute url forURL_type 0x00 supports the query parameter svc=<service_id> whereservice_id corresponds to the serviceId attribute for the parent Serviceelement.

@slsPlpId can be a string representing an integer number indicating thePLP ID of the physical layer pipe carrying the SLS for this service.

@slsDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying SLS data for this service.

@slsDestinationUdpPort can be a string containing the port number of thepackets carrying SLS data for this service. As described in theforegoing, SLS bootstrapping may be performed by destination IP/UDPinformation.

@slsSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying SLS data for this service.

@slsMajorProtocolVersion can be major version number of the protocolused to deliver the service layer signaling for this service. Defaultvalue is 1.

@SlsMinorProtocolVersion can be minor version number of the protocolused to deliver the service layer signaling for this service. Defaultvalue is 0.

@serviceLanguage can be a three-character language code indicating theprimary language of the service. A value of this field may have a formthat varies depending on embodiments.

@broadbandAccessRequired can be a Boolean indicating that broadbandaccess is required for a receiver to make a meaningful presentation ofthe service. Default value is false. When this field has a value ofTrue, the receiver needs to access a broadband for significant servicereproduction, which may correspond to a case of hybrid service delivery.

@capabilities can represent required capabilities for decoding andmeaningfully presenting the content for the service with service IDequal to the service Id attribute above.

InetSigLoc can provide a URL for access to signaling or announcementinformation via broadband, if available. Its data type can be anextension of the any URL data type, adding an @urlType attribute thatindicates what the URL gives access to. An @urlType field of this fieldmay indicate the same meaning as that of the @urlType field ofInetSigLoc described above. When an InetSigLoc element of attributeURL_type 0x00 is present as an element of the SLT, it can be used tomake HTTP requests for signaling metadata. The HTTP POST message bodymay include a service term. When the InetSigLoc element appears at thesection level, the service term is used to indicate the service to whichthe requested signaling metadata objects apply. If the service term isnot present, then the signaling metadata objects for all services in thesection are requested. When the InetSigLoc appears at the service level,then no service term is needed to designate the desired service. When anInetSigLoc element of attribute URL_type 0x01 is provided, it can beused to retrieve ESG data via broadband. If the element appears as achild element of the service element, then the URL can be used toretrieve ESG data for that service. If the element appears as a childelement of the SLT element, then the URL can be used to retrieve ESGdata for all services in that section.

In another example of the SLT, @sltSectionVersion, @sltSectionNumber,@totalSltSectionNumbers and/or @language fields of the SLT may beomitted.

In addition, the above-described InetSigLoc field may be replaced by@sltInetSigUri and/or @sltInetEsgUri field. The two fields may includethe URI of the signaling server and URI information of the ESG server,respectively. The InetSigLoc field corresponding to a lower field of theSLT and the InetSigLoc field corresponding to a lower field of theservice field may be replaced in a similar manner.

The suggested default values may vary depending on embodiments. Anillustrated “use” column relates to the respective fields. Here, “1” mayindicate that a corresponding field is an essential field, and “0 . . .1” may indicate that a corresponding field is an optional field.

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention.

Hereinafter, SLS will be described.

SLS can be signaling which provides information for discovery andacquisition of services and their content components.

For ROUTE/DASH, the SLS for each service describes characteristics ofthe service, such as a list of its components and where to acquire them,and the receiver capabilities required to make a meaningful presentationof the service. In the ROUTE/DASH system, the SLS includes the userservice bundle description (USBD), the S-TSID and the DASH mediapresentation description (MPD). Here, USBD or user service description(USD) is one of SLS XML fragments, and may function as a signaling herbthat describes specific descriptive information. USBD/USD may beextended beyond 3GPP MBMS. Details of USBD/USD will be described below.

The service signaling focuses on basic attributes of the service itself,especially those attributes needed to acquire the service. Properties ofthe service and programming that are intended for viewers appear asservice announcement, or ESG data.

Having separate Service Signaling for each service permits a receiver toacquire the appropriate SLS for a service of interest without the needto parse the entire SLS carried within a broadcast stream.

For optional broadband delivery of Service Signaling, the SLT caninclude HTTP URLs where the Service Signaling files can be obtained, asdescribed above.

LLS is used for bootstrapping SLS acquisition, and subsequently, the SLSis used to acquire service components delivered on either ROUTE sessionsor MMTP sessions. The described figure illustrates the followingsignaling sequences. Receiver starts acquiring the SLT described above.Each service identified by service id delivered over ROUTE sessionsprovides SLS bootstrapping information: PLPID(#1), source IP address(sIP1), destination IP address (dIP1), and destination port number(dPort1). Each service identified by service_id delivered over MMTPsessions provides SLS bootstrapping information: PLPID(#2), destinationIP address (dIP2), and destination port number (dPort2).

For streaming services delivery using ROUTE, the receiver can acquireSLS fragments carried over the IP/UDP/LCT session and PLP; whereas forstreaming services delivery using MMTP, the receiver can acquire SLSfragments carried over an MMTP session and PLP. For service deliveryusing ROUTE, these SLS fragments include USBD/USD fragments, S-TSIDfragments, and MPD fragments. They are relevant to one service. USBD/USDfragments describe service layer properties and provide URI referencesto S-TSID fragments and URI references to MPD fragments. In other words,the USBD/USD may refer to S-TSID and MPD. For service delivery usingMMTP, the USBD references the MMT signaling's MPT message, the MP Tableof which provides identification of package ID and location informationfor assets belonging to the service. Here, an asset is a multimedia dataentity, and may refer to a data entity which is combined into one uniqueID and is used to generate one multimedia presentation. The asset maycorrespond to a service component included in one service. The MPTmessage is a message having the MP table of MMT. Here, the MP table maybe an MMT package table having information about content and an MMTasset. Details may be similar to a definition in MMT. Here, mediapresentation may correspond to a collection of data that establishesbounded/unbounded presentation of media content.

The S-TSID fragment provides component acquisition informationassociated with one service and mapping between DASH Representationsfound in the MPD and in the TSI corresponding to the component of theservice. The S-TSID can provide component acquisition information in theform of a TSI and the associated DASH representation identifier, andPLPID carrying DASH segments associated with the DASH representation. Bythe PLPID and TSI values, the receiver collects the audio/videocomponents from the service and begins buffering DASH media segmentsthen applies the appropriate decoding processes.

For USBD listing service components delivered on MMTP sessions, asillustrated by “Service #2” in the described figure, the receiver alsoacquires an MPT message with matching MMT_package_id to complete theSLS. An MPT message provides the full list of service componentscomprising a service and the acquisition information for each component.Component acquisition information includes MMTP session information, thePLPID carrying the session and the packet_id within that session.

According to a given embodiment, for example, in ROUTE, two or moreS-TSID fragments may be used. Each fragment may provide accessinformation related to LCT sessions delivering content of each service.

In ROUTE, S-TSID, USBD/USD, MPD, or an LCT session delivering S-TSID,USBD/USD or MPD may be referred to as a service signaling channel. InMMTP, USBD/UD, an MMT signaling message, or a packet flow delivering theMMTP or USBD/UD may be referred to as a service signaling channel.

Unlike the illustrated example, one ROUTE or MMTP session may bedelivered through a plurality of PLPs. In other words, one service maybe delivered through one or more PLPs. As described in the foregoing,one LCT session may be delivered through one PLP. Unlike the figure,according to a given embodiment, components included in one service maybe delivered through different ROUTE sessions. In addition, according toa given embodiment, components included in one service may be deliveredthrough different MMTP sessions. According to a given embodiment,components included in one service may be delivered separately through aROUTE session and an MMTP session. Although not illustrated, componentsincluded in one service may be delivered via broadband (hybriddelivery).

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of SLS in delivery based onROUTE.

SLS provides detailed technical information to the receiver to enablethe discovery and access of services and their content components. Itcan include a set of XML-encoded metadata fragments carried over adedicated LCT session. That LCT session can be acquired using thebootstrap information contained in the SLT as described above. The SLSis defined on a per-service level, and it describes the characteristicsand access information of the service, such as a list of its contentcomponents and how to acquire them, and the receiver capabilitiesrequired to make a meaningful presentation of the service. In theROUTE/DASH system, for linear services delivery, the SLS consists of thefollowing metadata fragments: USBD, S-TSID and the DASH MPD. The SLSfragments can be delivered on a dedicated LCT transport session withTSI=0. According to a given embodiment, a TSI of a particular LCTsession (dedicated LCT session) in which an SLS fragment is deliveredmay have a different value. According to a given embodiment, an LCTsession in which an SLS fragment is delivered may be signaled using theSLT or another scheme.

ROUTE/DASH SLS can include the user service bundle description (USBD)and service-based transport session instance description (S-TSID)metadata fragments. These service signaling fragments are applicable toboth linear and application-based services. The USBD fragment containsservice identification, device capabilities information, references toother SLS fragments required to access the service and constituent mediacomponents, and metadata to enable the receiver to determine thetransport mode (broadcast and/or broadband) of service components. TheS-TSID fragment, referenced by the USBD, provides transport sessiondescriptions for the one or more ROUTE/LCT sessions in which the mediacontent components of a service are delivered, and descriptions of thedelivery objects carried in those LCT sessions. The USBD and S-TSID willbe described below.

In streaming content signaling in ROUTE-based delivery, a streamingcontent signaling component of SLS corresponds to an MPD fragment. TheMPD is typically associated with linear services for the delivery ofDASH Segments as streaming content. The MPD provides the resourceidentifiers for individual media components of the linear/streamingservice in the form of Segment URLs, and the context of the identifiedresources within the Media Presentation. Details of the MPD will bedescribed below.

In app-based enhancement signaling in ROUTE-based delivery, app-basedenhancement signaling pertains to the delivery of app-based enhancementcomponents, such as an application logic file, locally-cached mediafiles, network content items, or a notification stream. An applicationcan also retrieve locally-cached data over a broadband connection whenavailable.

Hereinafter, a description will be given of details of USBD/USDillustrated in the figure.

The top level or entry point SLS fragment is the USBD fragment. Anillustrated USBD fragment is an example of the present invention, basicfields of the USBD fragment not illustrated in the figure may beadditionally provided according to a given embodiment. As described inthe foregoing, the illustrated USBD fragment has an extended form, andmay have fields added to a basic configuration.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may correspond to aninstance for one service.

The userServiceDescription element may include @serviceId,@atsc:serviceId, @atsc:serviceStatus, @atsc:fullMPDUri, @atsc:sTSIDUri,name, serviceLanguage, atsc:capabilityCode and/or deliveryMethod.

@serviceId can be a globally unique URI that identifies a service,unique within the scope of the BSID. This parameter can be used to linkto ESG data (Service@globalServiceID).

@atsc:serviceId is a reference to corresponding service entry inLLS(SLT). The value of this attribute is the same value of serviceIdassigned to the entry.

@atsc:serviceStatus can specify the status of this service. The valueindicates whether this service is active or inactive. When set to “1”(true), that indicates service is active. When this field is not used,@atsc:serviceStatus may be set to a default value of 1.

@atsc:fullMPDUri can reference an MPD fragment which containsdescriptions for contents components of the service delivered overbroadcast and optionally, also over broadband.

@atsc:sTSIDUri can reference the S-TSID fragment which provides accessrelated parameters to the Transport sessions carrying contents of thisservice.

name can indicate name of the service as given by the lang attribute.name element can include lang attribute, which indicating language ofthe service name. The language can be specified according to XML datatypes.

serviceLanguage can represent available languages of the service. Thelanguage can be specified according to XML data types.

atsc:capabilityCode can specify the capabilities required in thereceiver to be able to create a meaningful presentation of the contentof this service. According to a given embodiment, this field may specifya predefined capability group. Here, the capability group may be a groupof capability attribute values for significant presentation. This fieldmay be omitted according to a given embodiment.

deliveryMethod can be a container of transport related informationpertaining to the contents of the service over broadcast and(optionally) broadband modes of access. Referring to data included inthe service, when the number of the data is N, delivery schemes forrespective data may be described by this element. The deliveryMethod mayinclude an r12:broadcastAppService element and an r12:unicastAppServiceelement. Each lower element may include a basePattern element as a lowerelement.

r12:broadcastAppService can be a DASH Representation delivered overbroadcast, in multiplexed or non-multiplexed form, containing thecorresponding media component(s) belonging to the service, across allPeriods of the affiliated media presentation. In other words, each ofthe fields may indicate DASH representation delivered through thebroadcast network.

r12:unicastAppService can be a DASH Representation delivered overbroadband, in multiplexed or non-multiplexed form, containing theconstituent media content component(s) belonging to the service, acrossall periods of the affiliated media presentation. In other words, eachof the fields may indicate DASH representation delivered via broadband.

basePattern can be a character pattern for use by the receiver to matchagainst any portion of the segment URL used by the DASH client torequest media segments of a parent representation under its containingperiod. A match implies that the corresponding requested media segmentis carried over broadcast transport. In a URL address for receiving DASHrepresentation expressed by each of the r12:broadcastAppService elementand the r12:unicastAppService element, a part of the URL, etc. may havea particular pattern. The pattern may be described by this field. Somedata may be distinguished using this information. The proposed defaultvalues may vary depending on embodiments. The “use” column illustratedin the figure relates to each field. Here, M may denote an essentialfield, O may denote an optional field, OD may denote an optional fieldhaving a default value, and CM may denote a conditional essential field.0 . . . 1 to 0 . . . N may indicate the number of available fields.

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of the S-TSID illustrated inthe figure in detail.

S-TSID can be an SLS XML fragment which provides the overall sessiondescription information for transport session(s) which carry the contentcomponents of a service. The S-TSID is the SLS metadata fragment thatcontains the overall transport session description information for thezero or more ROUTE sessions and constituent LCT sessions in which themedia content components of a service are delivered. The S-TSID alsoincludes file metadata for the delivery object or object flow carried inthe LCT sessions of the service, as well as additional information onthe payload formats and content components carried in those LCTsessions.

Each instance of the S-TSID fragment is referenced in the USBD fragmentby the @atsc:sTSIDUri attribute of the userServiceDescription element.The illustrated S-TSID according to the present embodiment is expressedas an XML document. According to a given embodiment, the S-TSID may beexpressed in a binary format or as an XML document.

The illustrated S-TSID may have an S-TSID root element. The S-TSID rootelement may include @serviceId and/or RS.

@serviceID can be a reference corresponding service element in the USD.The value of this attribute can reference a service with a correspondingvalue of service_id.

The RS element may have information about a ROUTE session for deliveringthe service data. Service data or service components may be deliveredthrough a plurality of ROUTE sessions, and thus the number of RSelements may be 1 to N.

The RS element may include @bsid, @sIpAddr, @dIpAddr, @dport, @PLPIDand/or LS.

@bsid can be an identifier of the broadcast stream within which thecontent component(s) of the broadcastAppService are carried. When thisattribute is absent, the default broadcast stream is the one whose PLPscarry SLS fragments for this service. Its value can be identical to thatof the broadcast_stream_id in the SLT.

@sIpAddr can indicate source IP address. Here, the source IP address maybe a source IP address of a ROUTE session for delivering a servicecomponent included in the service. As described in the foregoing,service components of one service may be delivered through a pluralityof ROUTE sessions. Thus, the service components may be transmitted usinganother ROUTE session other than the ROUTE session for delivering theS-TSID. Therefore, this field may be used to indicate the source IPaddress of the ROUTE session. A default value of this field may be asource IP address of a current ROUTE session. When a service componentis delivered through another ROUTE session, and thus the ROUTE sessionneeds to be indicated, a value of this field may be a value of a sourceIP address of the ROUTE session. In this case, this field may correspondto M, that is, an essential field.

@dIpAddr can indicate destination IP address. Here, a destination IPaddress may be a destination IP address of a ROUTE session that deliversa service component included in a service. For a similar case to theabove description of @sIpAddr, this field may indicate a destination IPaddress of a ROUTE session that delivers a service component. A defaultvalue of this field may be a destination IP address of a current ROUTEsession. When a service component is delivered through another ROUTEsession, and thus the ROUTE session needs to be indicated, a value ofthis field may be a value of a destination IP address of the ROUTEsession. In this case, this field may correspond to M, that is, anessential field.

@dport can indicate destination port. Here, a destination port may be adestination port of a ROUTE session that delivers a service componentincluded in a service. For a similar case to the above description of@sIpAddr, this field may indicate a destination port of a ROUTE sessionthat delivers a service component. A default value of this field may bea destination port number of a current ROUTE session. When a servicecomponent is delivered through another ROUTE session, and thus the ROUTEsession needs to be indicated, a value of this field may be adestination port number value of the ROUTE session. In this case, thisfield may correspond to M, that is, an essential field.

@PLPID may be an ID of a PLP for a ROUTE session expressed by an RS. Adefault value may be an ID of a PLP of an LCT session including acurrent S-TSID. According to a given embodiment, this field may have anID value of a PLP for an LCT session for delivering an S-TSID in theROUTE session, and may have ID values of all PLPs for the ROUTE session.

An LS element may have information about an LCT session for delivering aservice data. Service data or service components may be deliveredthrough a plurality of LCT sessions, and thus the number of LS elementsmay be 1 to N.

The LS element may include @tsi, @PLPID, @bw, @startTime, @endTime,SrcFlow and/or RprFlow.

@tsi may indicate a TSI value of an LCT session for delivering a servicecomponent of a service.

@PLPID may have ID information of a PLP for the LCT session. This valuemay be overwritten on a basic ROUTE session value.

@bw may indicate a maximum bandwidth value. @startTime may indicate astart time of the LCT session. @endTime may indicate an end time of theLCT session. A SrcFlow element may describe a source flow of ROUTE. ARprFlow element may describe a repair flow of ROUTE.

The proposed default values may be varied according to an embodiment.The “use” column illustrated in the figure relates to each field. Here,M may denote an essential field, O may denote an optional field, OD maydenote an optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for ROUTE/DASH.

The MPD is an SLS metadata fragment which contains a formalizeddescription of a DASH Media Presentation, corresponding to a linearservice of a given duration defined by the broadcaster (for example asingle TV program, or the set of contiguous linear TV programs over aperiod of time). The contents of the MPD provide the resourceidentifiers for Segments and the context for the identified resourceswithin the Media Presentation. The data structure and semantics of theMPD fragment can be according to the MPD defined by MPEG DASH.

One or more of the DASH Representations conveyed in the MPD can becarried over broadcast. The MPD may describe additional Representationsdelivered over broadband, e.g. in the case of a hybrid service, or tosupport service continuity in handoff from broadcast to broadcast due tobroadcast signal degradation (e.g. driving through a tunnel).

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention.

MMT SLS for linear services comprises the USBD fragment and the MMTPackage (MP) table. The MP table is as described above. The USBDfragment contains service identification, device capabilitiesinformation, references to other SLS information required to access theservice and constituent media components, and the metadata to enable thereceiver to determine the transport mode (broadcast and/or broadband) ofthe service components. The MP table for MPU components, referenced bythe USBD, provides transport session descriptions for the MMTP sessionsin which the media content components of a service are delivered and thedescriptions of the Assets carried in those MMTP sessions.

The streaming content signaling component of the SLS for MPU componentscorresponds to the MP table defined in MMT. The MP table provides a listof MMT assets where each asset corresponds to a single service componentand the description of the location information for this component.

USBD fragments may also contain references to the S-TSID and the MPD asdescribed above, for service components delivered by the ROUTE protocoland the broadband, respectively. According to a given embodiment, indelivery through MMT, a service component delivered through the ROUTEprotocol is NRT data, etc. Thus, in this case, MPD may be unnecessary.In addition, in delivery through MMT, information about an LCT sessionfor delivering a service component, which is delivered via broadband, isunnecessary, and thus an S-TSID may be unnecessary. Here, an MMT packagemay be a logical collection of media data delivered using MMT. Here, anMMTP packet may refer to a formatted unit of media data delivered usingMMT. An MPU may refer to a generic container of independently decodabletimed/non-timed data. Here, data in the MPU is media codec agnostic.

Hereinafter, a description will be given of details of the USBD/USDillustrated in the figure.

The illustrated USBD fragment is an example of the present invention,and basic fields of the USBD fragment may be additionally providedaccording to an embodiment. As described in the foregoing, theillustrated USBD fragment has an extended form, and may have fieldsadded to a basic structure.

The illustrated USBD according to an embodiment of the present inventionis expressed as an XML document. According to a given embodiment, theUSBD may be expressed in a binary format or as an XML document.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may be an instance for oneservice.

The userServiceDescription element may include @serviceId,@atsc:serviceId, name, serviceLanguage, atsc:capabilityCode,atsc:Channel, atsc:mpuComponent, atsc:routeComponent,atsc:broadbandComponent and/or atsc:ComponentInfo.

Here, @serviceId, @atsc:serviceId, name, serviceLanguage, andatsc:capabilityCode may be as described above. The lang field below thename field may be as described above. atsc:capabilityCode may be omittedaccording to a given embodiment.

The userServiceDescription element may further include anatsc:contentAdvisoryRating element according to an embodiment. Thiselement may be an optional element. atsc:contentAdvisoryRating canspecify the content advisory rating. This field is not illustrated inthe figure.

atsc:Channel may have information about a channel of a service. Theatsc:Channel element may include @atsc:majorChannelNo,@atsc:minorChannelNo, @atsc:serviceLang, @atsc:serviceGenre,@atsc:serviceIcon and/or atsc:ServiceDescription. @atsc:majorChannelNo,@atsc:minorChannelNo, and @atsc:serviceLang may be omitted according toa given embodiment.

@atsc:majorChannelNo is an attribute that indicates the major channelnumber of the service.

@atsc:minorChannelNo is an attribute that indicates the minor channelnumber of the service.

@atsc:serviceLang is an attribute that indicates the primary languageused in the service.

@atsc:serviceGenre is an attribute that indicates primary genre of theservice.

@atsc:serviceIcon is an attribute that indicates the Uniform ResourceLocator (URL) for the icon used to represent this service.

atsc:ServiceDescription includes service description, possibly inmultiple languages. atsc:ServiceDescription includes can include@atsc:serviceDescrText and/or @atsc:serviceDescrLang.

@atsc:serviceDescrText is an attribute that indicates description of theservice.

@atsc:serviceDescrLang is an attribute that indicates the language ofthe serviceDescrText attribute above.

atsc:mpuComponent may have information about a content component of aservice delivered in a form of an MPU. atsc:mpuComponent may include@atsc:mmtPackageId and/or @atsc:nextMmtPackageId.

@atsc:mmtPackageId can reference a MMT Package for content components ofthe service delivered as MPUs.

@atsc:nextMmtPackageId can reference a MMT Package to be used after theone referenced by @atsc:mmtPackageId in time for content components ofthe service delivered as MPUs.

atsc:routeComponent may have information about a content component of aservice delivered through ROUTE. atsc:routeComponent may include@atsc:sTSIDUri, @sTSIDPlpId, @sTSIDDestinationIpAddress,@sTSIDDestinationUdpPort, @sTSIDSourceIpAddress,@sTSIDMajorProtocolVersion and/or @sTSIDMinorProtocolVersion.

@atsc:sTSIDUri can be a reference to the S-TSID fragment which providesaccess related parameters to the Transport sessions carrying contents ofthis service. This field may be the same as a URI for referring to anS-TSID in USBD for ROUTE described above. As described in the foregoing,in service delivery by the MMTP, service components, which are deliveredthrough NRT, etc., may be delivered by ROUTE. This field may be used torefer to the S-TSID therefore.

@sTSIDPlpId can be a string representing an integer number indicatingthe PLP ID of the physical layer pipe carrying the S-TSID for thisservice. (default: current physical layer pipe).

@sTSIDDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying S-TSID for this service.(default: current MMTP session's source IP address).

@sTSIDDestinationUdpPort can be a string containing the port number ofthe packets carrying S-TSID for this service.

@sTSIDSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying S-TSID for this service.

@sTSIDMajorProtocolVersion can indicate major version number of theprotocol used to deliver the S-TSID for this service. Default value is1.

@sTSIDMinorProtocolVersion can indicate minor version number of theprotocol used to deliver the S-TSID for this service. Default value is0.

atsc:broadbandComponent may have information about a content componentof a service delivered via broadband. In other words,atsc:broadbandComponent may be a field on the assumption of hybriddelivery. atsc:broadbandComponent may further include @atsc:fullfMPDUri.

@atsc:fullfMPDUri can be a reference to an MPD fragment which containsdescriptions for contents components of the service delivered overbroadband.

An atsc:ComponentInfo field may have information about an availablecomponent of a service. The atsc:ComponentInfo field may haveinformation about a type, a role, a name, etc. of each component. Thenumber of atsc:ComponentInfo fields may correspond to the number (N) ofrespective components. The atsc:ComponentInfo field may include@atsc:componentType, @atsc:componentRole, @atsc:componentProtectedFlag,@atsc:componentId and/or @atsc:componentName.

@atsc:componentType is an attribute that indicates the type of thiscomponent. Value of 0 indicates an audio component. Value of 1 indicatesa video component. Value of 2 indicated a closed caption component.Value of 3 indicates an application component. Values 4 to 7 arereserved. A meaning of a value of this field may be differently setdepending on embodiments.

@atsc:componentRole is an attribute that indicates the role or kind ofthis component.

For audio (when componentType attribute above is equal to 0): values ofcomponentRole attribute are as follows: 0=Complete main, 1=Music andEffects, 2=Dialog, 3=Commentary, 4=Visually Impaired, 5=HearingImpaired, 6=Voice-Over, 7-254=reserved, 255=unknown.

For video (when componentType attribute above is equal to 1) values ofcomponentRole attribute are as follows: 0=Primary video, 1=Alternativecamera view, 2=Other alternative video component, 3=Sign language inset,4=Follow subject video, 5=3D video left view, 6=3D video right view,7=3D video depth information, 8=Part of video array <x,y> of <n,m>,9=Follow-Subject metadata, 10-254=reserved, 255=unknown.

For Closed Caption component (when componentType attribute above isequal to 2) values of componentRole attribute are as follows: 0=Normal,1=Easy reader, 2-254=reserved, 255=unknown.

When componentType attribute above is between 3 to 7, inclusive, thecomponentRole can be equal to 255. A meaning of a value of this fieldmay be differently set depending on embodiments.

@atsc:componentProtectedFlag is an attribute that indicates if thiscomponent is protected (e.g. encrypted). When this flag is set to avalue of 1 this component is protected (e.g. encrypted). When this flagis set to a value of 0 this component is not protected (e.g. encrypted).When not present the value of componentProtectedFlag attribute isinferred to be equal to 0. A meaning of a value of this field may bedifferently set depending on embodiments.

@atsc:componentId is an attribute that indicates the identifier of thiscomponent. The value of this attribute can be the same as the asset_idin the MP table corresponding to this component.

@atsc:componentName is an attribute that indicates the human readablename of this component.

The proposed default values may vary depending on embodiments. The “use”column illustrated in the figure relates to each field. Here, M maydenote an essential field, O may denote an optional field, OD may denotean optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for MMT.

The Media Presentation Description is an SLS metadata fragmentcorresponding to a linear service of a given duration defined by thebroadcaster (for example a single TV program, or the set of contiguouslinear TV programs over a period of time). The contents of the MPDprovide the resource identifiers for segments and the context for theidentified resources within the media presentation. The data structureand semantics of the MPD can be according to the MPD defined by MPEGDASH.

In the present embodiment, an MPD delivered by an MMTP session describesRepresentations delivered over broadband, e.g. in the case of a hybridservice, or to support service continuity in handoff from broadcast tobroadband due to broadcast signal degradation (e.g. driving under amountain or through a tunnel).

Hereinafter, a description will be given of an MMT signaling message forMMT.

When MMTP sessions are used to carry a streaming service, MMT signalingmessages defined by MMT are delivered by MMTP packets according tosignaling message mode defined by MMT. The value of the packet_id fieldof MMTP packets carrying service layer signaling is set to ‘00’ exceptfor MMTP packets carrying MMT signaling messages specific to an asset,which can be set to the same packet_id value as the MMTP packetscarrying the asset. Identifiers referencing the appropriate package foreach service are signaled by the USBD fragment as described above. MMTPackage Table (MPT) messages with matching MMT_package_id can bedelivered on the MMTP session signaled in the SLT. Each MMTP sessioncarries MMT signaling messages specific to its session or each assetdelivered by the MMTP session.

In other words, it is possible to access USBD of the MMTP session byspecifying an IP destination address/port number, etc. of a packethaving the SLS for a particular service in the SLT. As described in theforegoing, a packet ID of an MMTP packet carrying the SLS may bedesignated as a particular value such as 00, etc. It is possible toaccess an MPT message having a matched packet ID using theabove-described package IP information of USBD. As described below, theMPT message may be used to access each service component/asset.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT.

MMT Package Table (MPT) message: This message carries an MP (MMTPackage) table which contains the list of all Assets and their locationinformation as defined by MMT. If an Asset is delivered by a PLPdifferent from the current PLP delivering the MP table, the identifierof the PLP carrying the asset can be provided in the MP table usingphysical layer pipe identifier descriptor. The physical layer pipeidentifier descriptor will be described below.

MMT ATSC3 (MA3) message mmt_atsc3_message( ): This message carriessystem metadata specific for services including service layer signalingas described above. mmt_atsc3_message( ) will be described below.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT, if required.

Media Presentation Information (MPI) message: This message carries anMPI table which contains the whole document or a subset of a document ofpresentation information. An MP table associated with the MPI table alsocan be delivered by this message.

Clock Relation Information (CRI) message: This message carries a CRItable which contains clock related information for the mapping betweenthe NTP timestamp and the MPEG-2 STC. According to a given embodiment,the CRI message may not be delivered through the MMTP session.

The following MMTP messages can be delivered by each MMTP sessioncarrying streaming content.

Hypothetical Receiver Buffer Model message: This message carriesinformation required by the receiver to manage its buffer.

Hypothetical Receiver Buffer Model Removal message: This message carriesinformation required by the receiver to manage its MMT de-capsulationbuffer.

Hereinafter, a description will be given of mmt_atsc3_message( )corresponding to one of MMT signaling messages. An MMT Signaling messagemmt_atsc3_message( ) is defined to deliver information specific toservices according to the present invention described above. Thesignaling message may include message ID, version, and/or length fieldscorresponding to basic fields of the MMT signaling message. A payload ofthe signaling message may include service ID information, content typeinformation, content version information, content compressioninformation and/or URI information. The content type information mayindicate a type of data included in the payload of the signalingmessage. The content version information may indicate a version of dataincluded in the payload, and the content compression information mayindicate a type of compression applied to the data. The URI informationmay have URI information related to content delivered by the message.

Hereinafter, a description will be given of the physical layer pipeidentifier descriptor.

The physical layer pipe identifier descriptor is a descriptor that canbe used as one of descriptors of the MP table described above. Thephysical layer pipe identifier descriptor provides information about thePLP carrying an asset. If an asset is delivered by a PLP different fromthe current PLP delivering the MP table, the physical layer pipeidentifier descriptor can be used as an asset descriptor in theassociated MP table to identify the PLP carrying the asset. The physicallayer pipe identifier descriptor may further include BSID information inaddition to PLP ID information. The BSID may be an ID of a broadcaststream that delivers an MMTP packet for an asset described by thedescriptor.

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention.

Hereinafter, a link layer will be described.

The link layer is the layer between the physical layer and the networklayer, and transports the data from the network layer to the physicallayer at the sending side and transports the data from the physicallayer to the network layer at the receiving side. The purpose of thelink layer includes abstracting all input packet types into a singleformat for processing by the physical layer, ensuring flexibility andfuture extensibility for as yet undefined input types. In addition,processing within the link layer ensures that the input data can betransmitted in an efficient manner, for example by providing options tocompress redundant information in the headers of input packets. Theoperations of encapsulation, compression and so on are referred to asthe link layer protocol and packets created using this protocol arecalled link layer packets. The link layer may perform functions such aspacket encapsulation, overhead reduction and/or signaling transmission,etc.

Hereinafter, packet encapsulation will be described. Link layer protocolallows encapsulation of any type of packet, including ones such as IPpackets and MPEG-2 TS. Using link layer protocol, the physical layerneed only process one single packet format, independent of the networklayer protocol type (here we consider MPEG-2 TS packet as a kind ofnetwork layer packet.) Each network layer packet or input packet istransformed into the payload of a generic link layer packet.Additionally, concatenation and segmentation can be performed in orderto use the physical layer resources efficiently when the input packetsizes are particularly small or large.

As described in the foregoing, segmentation may be used in packetencapsulation. When the network layer packet is too large to processeasily in the physical layer, the network layer packet is divided intotwo or more segments. The link layer packet header includes protocolfields to perform segmentation on the sending side and reassembly on thereceiving side. When the network layer packet is segmented, each segmentcan be encapsulated to link layer packet in the same order as originalposition in the network layer packet. Also each link layer packet whichincludes a segment of network layer packet can be transported to PHYlayer consequently.

As described in the foregoing, concatenation may be used in packetencapsulation. When the network layer packet is small enough for thepayload of a link layer packet to include several network layer packets,the link layer packet header includes protocol fields to performconcatenation. The concatenation is combining of multiple small sizednetwork layer packets into one payload. When the network layer packetsare concatenated, each network layer packet can be concatenated topayload of link layer packet in the same order as original input order.Also each packet which constructs a payload of link layer packet can bewhole packet, not a segment of packet.

Hereinafter, overhead reduction will be described. Use of the link layerprotocol can result in significant reduction in overhead for transportof data on the physical layer. The link layer protocol according to thepresent invention may provide IP overhead reduction and/or MPEG-2 TSoverhead reduction. In IP overhead reduction, IP packets have a fixedheader format, however some of the information which is needed in acommunication environment may be redundant in a broadcast environment.Link layer protocol provides mechanisms to reduce the broadcast overheadby compressing headers of IP packets. In MPEG-2 TS overhead reduction,link layer protocol provides sync byte removal, null packet deletionand/or common header removal (compression). First, sync byte removalprovides an overhead reduction of one byte per TS packet, secondly anull packet deletion mechanism removes the 188 byte null TS packets in amanner that they can be re-inserted at the receiver and finally a commonheader removal mechanism.

For signaling transmission, in the link layer protocol, a particularformat for the signaling packet may be provided for link layersignaling, which will be described below.

In the illustrated link layer protocol architecture according to anembodiment of the present invention, link layer protocol takes as inputnetwork layer packets such as IPv4, MPEG-2 TS and so on as inputpackets. Future extension indicates other packet types and protocolwhich is also possible to be input in link layer. Link layer protocolalso specifies the format and signaling for any link layer signaling,including information about mapping to specific channel to the physicallayer. Figure also shows how ALP incorporates mechanisms to improve theefficiency of transmission, via various header compression and deletionalgorithms. In addition, the link layer protocol may basicallyencapsulate input packets.

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention. Hereinafter, thestructure of the header will be described.

A link layer packet can include a header followed by the data payload.The header of a link layer packet can include a base header, and mayinclude an additional header depending on the control fields of the baseheader. The presence of an optional header is indicated from flag fieldsof the additional header. According to a given embodiment, a fieldindicating the presence of an additional header and an optional headermay be positioned in the base header.

Hereinafter, the structure of the base header will be described. Thebase header for link layer packet encapsulation has a hierarchicalstructure. The base header can be two bytes in length and is the minimumlength of the link layer packet header.

The illustrated base header according to the present embodiment mayinclude a Packet_Type field, a PC field and/or a length field. Accordingto a given embodiment, the base header may further include an HM fieldor an S/C field.

Packet_Type field can be a 3-bit field that indicates the originalprotocol or packet type of the input data before encapsulation into alink layer packet. An IPv4 packet, a compressed IP packet, a link layersignaling packet, and other types of packets may have the base headerstructure and may be encapsulated. However, according to a givenembodiment, the MPEG-2 TS packet may have a different particularstructure, and may be encapsulated. When the value of Packet_Type is“000”, “001” “100” or “111”, that is the original data type of an ALPpacket is one of an IPv4 packet, a compressed IP packet, link layersignaling or extension packet. When the MPEG-2 TS packet isencapsulated, the value of Packet_Type can be “010”. Other values of thePacket_Type field may be reserved for future use.

Payload_Configuration (PC) field can be a 1-bit field that indicates theconfiguration of the payload. A value of 0 can indicate that the linklayer packet carries a single, whole input packet and the followingfield is the Header_Mode field. A value of 1 can indicate that the linklayer packet carries more than one input packet (concatenation) or apart of a large input packet (segmentation) and the following field isthe Segmentation_Concatenation field.

Header_Mode (HM) field can be a 1-bit field, when set to 0, that canindicate there is no additional header, and that the length of thepayload of the link layer packet is less than 2048 bytes. This value maybe varied depending on embodiments. A value of 1 can indicate that anadditional header for single packet defined below is present followingthe Length field. In this case, the length of the payload is larger than2047 bytes and/or optional features can be used (sub streamidentification, header extension, etc.). This value may be varieddepending on embodiments. This field can be present only whenPayload_Configuration field of the link layer packet has a value of 0.

Segmentation_Concatenation (S/C) field can be a 1-bit field, when set to0, that can indicate that the payload carries a segment of an inputpacket and an additional header for segmentation defined below ispresent following the Length field. A value of 1 can indicate that thepayload carries more than one complete input packet and an additionalheader for concatenation defined below is present following the Lengthfield. This field can be present only when the value ofPayload_Configuration field of the ALP packet is 1.

Length field can be an 11-bit field that indicates the 11 leastsignificant bits (LSBs) of the length in bytes of payload carried by thelink layer packet. When there is a Length_MSB field in the followingadditional header, the length field is concatenated with the Length_MSBfield, and is the LSB to provide the actual total length of the payload.The number of bits of the length field may be changed to another valuerather than 11 bits.

Following types of packet configuration are thus possible: a singlepacket without any additional header, a single packet with an additionalheader, a segmented packet and a concatenated packet. According to agiven embodiment, more packet configurations may be made through acombination of each additional header, an optional header, an additionalheader for signaling information to be described below, and anadditional header for time extension.

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention.

Various types of additional headers may be present. Hereinafter, adescription will be given of an additional header for a single packet.

This additional header for single packet can be present when Header_Mode(HM)=“1”. The Header Mode (HM) can be set to 1 when the length of thepayload of the link layer packet is larger than 2047 bytes or when theoptional fields are used. The additional header for single packet isshown in Figure (tsib10010).

Length_MSB field can be a 5-bit field that can indicate the mostsignificant bits (MSBs) of the total payload length in bytes in thecurrent link layer packet, and is concatenated with the Length fieldcontaining the 11 least significant bits (LSBs) to obtain the totalpayload length. The maximum length of the payload that can be signaledis therefore 65535 bytes. The number of bits of the length field may bechanged to another value rather than 11 bits. In addition, the number ofbits of the Length_MSB field may be changed, and thus a maximumexpressible payload length may be changed. According to a givenembodiment, each length field may indicate a length of a whole linklayer packet rather than a payload.

SIF (Sub stream Identifier Flag) field can be a 1-bit field that canindicate whether the sub stream ID (SID) is present after the HEF fieldor not. When there is no SID in this link layer packet, SIF field can beset to 0. When there is a SID after HEF field in the link layer packet,SIF can be set to 1. The detail of SID is described below.

HEF (Header Extension Flag) field can be a 1-bit field that canindicate, when set to 1 additional header is present for futureextension. A value of 0 can indicate that this extension header is notpresent.

Hereinafter, a description will be given of an additional header whensegmentation is used.

This additional header (tsib10020) can be present whenSegmentation_Concatenation (S/C)=“0”. Segment_Sequence_Number can be a5-bit unsigned integer that can indicate the order of the correspondingsegment carried by the link layer packet. For the link layer packetwhich carries the first segment of an input packet, the value of thisfield can be set to 0x0. This field can be incremented by one with eachadditional segment belonging to the segmented input packet.

Last_Segment_Indicator (LSI) can be a 1-bit field that can indicate,when set to 1, that the segment in this payload is the last one of inputpacket. A value of 0, can indicate that it is not last segment.

SIF (Sub stream Identifier Flag) can be a 1-bit field that can indicatewhether the SID is present after the HEF field or not. When there is noSID in the link layer packet, SIF field can be set to 0. When there is aSID after the HEF field in the link layer packet, SIF can be set to 1.

HEF (Header Extension Flag) can be a This 1-bit field that can indicate,when set to 1, that the optional header extension is present after theadditional header for future extensions of the link layer header. Avalue of 0 can indicate that optional header extension is not present.

According to a given embodiment, a packet ID field may be additionallyprovided to indicate that each segment is generated from the same inputpacket. This field may be unnecessary and thus be omitted when segmentsare transmitted in order.

Hereinafter, a description will be given of an additional header whenconcatenation is used.

This additional header (tsib10030) can be present whenSegmentation_Concatenation (S/C)=“1”.

Length_MSB can be a 4-bit field that can indicate MSB bits of thepayload length in bytes in this link layer packet. The maximum length ofthe payload is 32767 bytes for concatenation. As described in theforegoing, a specific numeric value may be changed.

Count can be a field that can indicate the number of the packetsincluded in the link layer packet. The number of the packets included inthe link layer packet, 2 can be set to this field. So, its maximum valueof concatenated packets in a link layer packet is 9. A scheme in whichthe count field indicates the number may be varied depending onembodiments. That is, the numbers from 1 to 8 may be indicated.

HEF (Header Extension Flag) can be a 1-bit field that can indicate, whenset to 1 the optional header extension is present after the additionalheader for future extensions of the link layer header. A value of 0, canindicate extension header is not present.

Component_Length can be a 12-bit length field that can indicate thelength in byte of each packet. Component_Length fields are included inthe same order as the packets present in the payload except lastcomponent packet. The number of length field can be indicated by(Count+1). According to a given embodiment, length fields, the number ofwhich is the same as a value of the count field, may be present. When alink layer header consists of an odd number of Component_Length, fourstuffing bits can follow after the last Component_Length field. Thesebits can be set to 0. According to a given embodiment, aComponent_length field indicating a length of a last concatenated inputpacket may not be present. In this case, the length of the lastconcatenated input packet may correspond to a length obtained bysubtracting a sum of values indicated by respective Component_lengthfields from a whole payload length.

Hereinafter, the optional header will be described.

As described in the foregoing, the optional header may be added to arear of the additional header. The optional header field can contain SIDand/or header extension. The SID is used to filter out specific packetstream in the link layer level. One example of SID is the role ofservice identifier in a link layer stream carrying multiple services.The mapping information between a service and the SID valuecorresponding to the service can be provided in the SLT, if applicable.The header extension contains extended field for future use. Receiverscan ignore any header extensions which they do not understand.

SID (Sub stream Identifier) can be an 8-bit field that can indicate thesub stream identifier for the link layer packet. If there is optionalheader extension, SID present between additional header and optionalheader extension.

Header_Extension ( ) can include the fields defined below.

Extension_Type can be an 8-bit field that can indicate the type of theHeader_Extension ( ).

Extension_Length can be an 8-bit field that can indicate the length ofthe Header Extension ( ) in bytes counting from the next byte to thelast byte of the Header_Extension ( ).

Extension_Byte can be a byte representing the value of theHeader_Extension ( ).

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention.

Hereinafter, a description will be given of an additional header forsignaling information.

How link layer signaling is incorporated into link layer packets are asfollows. Signaling packets are identified by when the Packet_Type fieldof the base header is equal to 100.

Figure (tsib11010) shows the structure of the link layer packetscontaining additional header for signaling information. In addition tothe link layer header, the link layer packet can consist of twoadditional parts, additional header for signaling information and theactual signaling data itself. The total length of the link layersignaling packet is shown in the link layer packet header.

The additional header for signaling information can include followingfields. According to a given embodiment, some fields may be omitted.

Signaling_Type can be an 8-bit field that can indicate the type ofsignaling.

Signaling_Type_Extension can be a 16-bit filed that can indicate theattribute of the signaling. Detail of this field can be defined insignaling specification.

Signaling_Version can be an 8-bit field that can indicate the version ofsignaling.

Signaling_Format can be a 2-bit field that can indicate the data formatof the signaling data. Here, a signaling format may refer to a dataformat such as a binary format, an XML format, etc.

Signaling_Encoding can be a 2-bit field that can specify theencoding/compression format. This field may indicate whether compressionis not performed and which type of compression is performed.

Hereinafter, a description will be given of an additional header forpacket type extension.

In order to provide a mechanism to allow an almost unlimited number ofadditional protocol and packet types to be carried by link layer in thefuture, the additional header is defined. Packet type extension can beused when Packet_type is 111 in the base header as described above.Figure (tsib11020) shows the structure of the link layer packetscontaining additional header for type extension.

The additional header for type extension can include following fields.According to a given embodiment, some fields may be omitted.

extended_type can be a 16-bit field that can indicate the protocol orpacket type of the input encapsulated in the link layer packet aspayload. This field cannot be used for any protocol or packet typealready defined by Packet_Type field.

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention.

Hereinafter, a description will be given of a format of the link layerpacket when the MPEG-2 TS packet is input as an input packet.

In this case, the Packet_Type field of the base header is equal to 010.Multiple TS packets can be encapsulated within each link layer packet.The number of TS packets is signaled via the NUMTS field. In this case,as described in the foregoing, a particular link layer packet headerformat may be used.

Link layer provides overhead reduction mechanisms for MPEG-2 TS toenhance the transmission efficiency. The sync byte (0x47) of each TSpacket can be deleted. The option to delete NULL packets and similar TSheaders is also provided.

In order to avoid unnecessary transmission overhead, TS null packets(PID=0x1FFF) may be removed. Deleted null packets can be recovered inreceiver side using DNP field. The DNP field indicates the count ofdeleted null packets. Null packet deletion mechanism using DNP field isdescribed below.

In order to achieve more transmission efficiency, similar header ofMPEG-2 TS packets can be removed. When two or more successive TS packetshave sequentially increased continuity counter fields and other headerfields are the same, the header is sent once at the first packet and theother headers are deleted. HDM field can indicate whether the headerdeletion is performed or not. Detailed procedure of common TS headerdeletion is described below.

When all three overhead reduction mechanisms are performed, overheadreduction can be performed in sequence of sync removal, null packetdeletion, and common header deletion. According to a given embodiment, aperformance order of respective mechanisms may be changed. In addition,some mechanisms may be omitted according to a given embodiment.

The overall structure of the link layer packet header when using MPEG-2TS packet encapsulation is depicted in Figure (tsib12010).

Hereinafter, a description will be given of each illustrated field.Packet_Type can be a 3-bit field that can indicate the protocol type ofinput packet as describe above. For MPEG-2 TS packet encapsulation, thisfield can always be set to 010.

NUMTS (Number of TS packets) can be a 4-bit field that can indicate thenumber of TS packets in the payload of this link layer packet. A maximumof 16 TS packets can be supported in one link layer packet. The value ofNUMTS=0 can indicate that 16 TS packets are carried by the payload ofthe link layer packet. For all other values of NUMTS, the same number ofTS packets are recognized, e.g. NUMTS=0001 means one TS packet iscarried.

AHF (Additional Header Flag) can be a field that can indicate whetherthe additional header is present of not. A value of 0 indicates thatthere is no additional header. A value of 1 indicates that an additionalheader of length 1-byte is present following the base header. If null TSpackets are deleted or TS header compression is applied this field canbe set to 1. The additional header for TS packet encapsulation consistsof the following two fields and is present only when the value of AHF inthis link layer packet is set to 1.

HDM (Header Deletion Mode) can be a 1-bit field that indicates whetherTS header deletion can be applied to this link layer packet. A value of1 indicates that TS header deletion can be applied. A value of “0”indicates that the TS header deletion method is not applied to this linklayer packet.

DNP (Deleted Null Packets) can be a 7-bit field that indicates thenumber of deleted null TS packets prior to this link layer packet. Amaximum of 128 null TS packets can be deleted. When HDM=0 the value ofDNP=0 can indicate that 128 null packets are deleted. When HDM=1 thevalue of DNP=0 can indicate that no null packets are deleted. For allother values of DNP, the same number of null packets are recognized,e.g. DNP=5 means 5 null packets are deleted.

The number of bits of each field described above may be changed.According to the changed number of bits, a minimum/maximum value of avalue indicated by the field may be changed. These numbers may bechanged by a designer.

Hereinafter, SYNC byte removal will be described.

When encapsulating TS packets into the payload of a link layer packet,the SYNC byte (0x47) from the start of each TS packet can be deleted.Hence the length of the MPEG2-TS packet encapsulated in the payload ofthe link layer packet is always of length 187 bytes (instead of 188bytes originally).

Hereinafter, null packet deletion will be described.

Transport Stream rules require that bit rates at the output of atransmitter's multiplexer and at the input of the receiver'sde-multiplexer are constant in time and the end-to-end delay is alsoconstant. For some Transport Stream input signals, null packets may bepresent in order to accommodate variable bitrate services in a constantbitrate stream. In this case, in order to avoid unnecessary transmissionoverhead, TS null packets (that is TS packets with PID=0x1FFF) may beremoved. The process is carried-out in a way that the removed nullpackets can be re-inserted in the receiver in the exact place where theywere originally, thus guaranteeing constant bitrate and avoiding theneed for PCR time stamp updating.

Before generation of a link layer packet, a counter called DNP (DeletedNull-Packets) can first be reset to zero and then incremented for eachdeleted null packet preceding the first non-null TS packet to beencapsulated into the payload of the current link layer packet. Then agroup of consecutive useful TS packets is encapsulated into the payloadof the current link layer packet and the value of each field in itsheader can be determined. After the generated link layer packet isinjected to the physical layer, the DNP is reset to zero. When DNPreaches its maximum allowed value, if the next packet is also a nullpacket, this null packet is kept as a useful packet and encapsulatedinto the payload of the next link layer packet. Each link layer packetcan contain at least one useful TS packet in its payload.

Hereinafter, TS packet header deletion will be described. TS packetheader deletion may be referred to as TS packet header compression.

When two or more successive TS packets have sequentially increasedcontinuity counter fields and other header fields are the same, theheader is sent once at the first packet and the other headers aredeleted. When the duplicated MPEG-2 TS packets are included in two ormore successive TS packets, header deletion cannot be applied intransmitter side. HDM field can indicate whether the header deletion isperformed or not. When TS header deletion is performed, HDM can be setto 1. In the receiver side, using the first packet header, the deletedpacket headers are recovered, and the continuity counter is restored byincreasing it in order from that of the first header.

An example tsib12020 illustrated in the figure is an example of aprocess in which an input stream of a TS packet is encapsulated into alink layer packet. First, a TS stream including TS packets having SYNCbyte (0x47) may be input. First, sync bytes may be deleted through async byte deletion process. In this example, it is presumed that nullpacket deletion is not performed.

Here, it is presumed that packet headers of eight TS packets have thesame field values except for CC, that is, a continuity counter fieldvalue. In this case, TS packet deletion/compression may be performed.Seven remaining TS packet headers are deleted except for a first TSpacket header corresponding to CC=1. The processed TS packets may beencapsulated into a payload of the link layer packet.

In a completed link layer packet, a Packet_Type field corresponds to acase in which TS packets are input, and thus may have a value of 010. ANUMTS field may indicate the number of encapsulated TS packets. An AHFfield may be set to 1 to indicate the presence of an additional headersince packet header deletion is performed. An HDM field may be set to 1since header deletion is performed. DNP may be set to 0 since nullpacket deletion is not performed.

FIG. 13 illustrates an example of adaptation modes in IP headercompression according to an embodiment of the present invention(transmitting side).

Hereinafter, IP header compression will be described.

In the link layer, IP header compression/decompression scheme can beprovided. IP header compression can include two parts: headercompressor/decompressor and adaptation module. The header compressionscheme can be based on the Robust Header Compression (RoHC). Inaddition, for broadcasting usage, adaptation function is added.

In the transmitter side, ROHC compressor reduces the size of header foreach packet. Then, adaptation module extracts context information andbuilds signaling information from each packet stream. In the receiverside, adaptation module parses the signaling information associated withthe received packet stream and attaches context information to thereceived packet stream. ROHC decompressor reconstructs the original IPpacket by recovering the packet header.

The header compression scheme can be based on the RoHC as describedabove. In particular, in the present system, an RoHC framework canoperate in a unidirectional mode (U mode) of the RoHC. In addition, inthe present system, it is possible to use an RoHC UDP header compressionprofile which is identified by a profile identifier of 0x0002.

Hereinafter, adaptation will be described.

In case of transmission through the unidirectional link, if a receiverhas no information of context, decompressor cannot recover the receivedpacket header until receiving full context. This may cause channelchange delay and turn on delay. For this reason, context information andconfiguration parameters between compressor and decompressor can bealways sent with packet flow.

The Adaptation function provides out-of-band transmission of theconfiguration parameters and context information. Out-of-bandtransmission can be done through the link layer signaling. Therefore,the adaptation function is used to reduce the channel change delay anddecompression error due to loss of context information.

Hereinafter, extraction of context information will be described.

Context information may be extracted using various schemes according toadaptation mode. In the present invention, three examples will bedescribed below. The scope of the present invention is not restricted tothe examples of the adaptation mode to be described below. Here, theadaptation mode may be referred to as a context extraction mode.

Adaptation Mode 1 (not illustrated) may be a mode in which no additionaloperation is applied to a basic RoHC packet stream. In other words, theadaptation module may operate as a buffer in this mode. Therefore, inthis mode, context information may not be included in link layersignaling.

In Adaptation Mode 2 (tsib13010), the adaptation module can detect theIR packet from ROHC packet flow and extract the context information(static chain). After extracting the context information, each IR packetcan be converted to an IR-DYN packet. The converted IR-DYN packet can beincluded and transmitted inside the ROHC packet flow in the same orderas IR packet, replacing the original packet.

In Adaptation Mode 3 (tsib13020), the adaptation module can detect theIR and IR-DYN packet from ROHC packet flow and extract the contextinformation. The static chain and dynamic chain can be extracted from IRpacket and dynamic chain can be extracted from IR-DYN packet. Afterextracting the context information, each IR and IR-DYN packet can beconverted to a compressed packet. The compressed packet format can bethe same with the next packet of IR or IR-DYN packet. The convertedcompressed packet can be included and transmitted inside the ROHC packetflow in the same order as IR or IR-DYN packet, replacing the originalpacket.

Signaling (context) information can be encapsulated based ontransmission structure. For example, context information can beencapsulated to the link layer signaling. In this case, the packet typevalue can be set to “100”.

In the above-described Adaptation Modes 2 and 3, a link layer packet forcontext information may have a packet type field value of 100. Inaddition, a link layer packet for compressed IP packets may have apacket type field value of 001. The values indicate that each of thesignaling information and the compressed IP packets are included in thelink layer packet as described above.

Hereinafter, a description will be given of a method of transmitting theextracted context information.

The extracted context information can be transmitted separately fromROHC packet flow, with signaling data through specific physical datapath. The transmission of context depends on the configuration of thephysical layer path. The context information can be sent with other linklayer signaling through the signaling data pipe.

In other words, the link layer packet having the context information maybe transmitted through a signaling PLP together with link layer packetshaving other link layer signaling information (Packet_Type=100).Compressed IP packets from which context information is extracted may betransmitted through a general PLP (Packet_Type=001). Here, depending onembodiments, the signaling PLP may refer to an L1 signaling path. Inaddition, depending on embodiments, the signaling PLP may not beseparated from the general PLP, and may refer to a particular andgeneral PLP through which the signaling information is transmitted.

At a receiving side, prior to reception of a packet stream, a receivermay need to acquire signaling information. When receiver decodes initialPLP to acquire the signaling information, the context signaling can bealso received. After the signaling acquisition is done, the PLP toreceive packet stream can be selected. In other words, the receiver mayacquire the signaling information including the context information byselecting the initial PLP. Here, the initial PLP may be theabove-described signaling PLP. Thereafter, the receiver may select a PLPfor acquiring a packet stream. In this way, the context information maybe acquired prior to reception of the packet stream.

After the PLP for acquiring the packet stream is selected, theadaptation module can detect IR-DYN packet form received packet flow.Then, the adaptation module parses the static chain from the contextinformation in the signaling data. This is similar to receiving the IRpacket. For the same context identifier, IR-DYN packet can be recoveredto IR packet. Recovered ROHC packet flow can be sent to ROHCdecompressor. Thereafter, decompression may be started.

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention.

Hereinafter, link layer signaling will be described.

Generally, link layer signaling is operates under IP level. At thereceiver side, link layer signaling can be obtained earlier than IPlevel signaling such as Service List Table (SLT) and Service LayerSignaling (SLS). Therefore, link layer signaling can be obtained beforesession establishment.

For link layer signaling, there can be two kinds of signaling accordinginput path: internal link layer signaling and external link layersignaling. The internal link layer signaling is generated in link layerat transmitter side. And the link layer takes the signaling fromexternal module or protocol. This kind of signaling information isconsidered as external link layer signaling. If some signaling need tobe obtained prior to IP level signaling, external signaling istransmitted in format of link layer packet.

The link layer signaling can be encapsulated into link layer packet asdescribed above. The link layer packets can carry any format of linklayer signaling, including binary and XML. The same signalinginformation may not be transmitted in different formats for the linklayer signaling.

Internal link layer signaling may include signaling information for linkmapping. The Link Mapping Table (LMT) provides a list of upper layersessions carried in a PLP. The LMT also provides addition informationfor processing the link layer packets carrying the upper layer sessionsin the link layer.

An example of the LMT (tsib14010) according to the present invention isillustrated.

signaling_type can be an 8-bit unsigned integer field that indicates thetype of signaling carried by this table. The value of signaling_typefield for Link Mapping Table (LMT) can be set to 0x01.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

num_session can be an 8-bit unsigned integer field that provides thenumber of upper layer sessions carried in the PLP identified by theabove PLP_ID field. When the value of signaling_type field is 0x01, thisfield can indicate the number of UDP/IP sessions in the PLP.

src_IP_add can be a 32-bit unsigned integer field that contains thesource IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_IP_add can be a 32-bit unsigned integer field that contains thedestination IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

src_UDP_port can be a 16-bit unsigned integer field that represents thesource UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_UDP_port can be a 16-bit unsigned integer field that represents thedestination UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

SID_flag can be a 1-bit Boolean field that indicates whether the linklayer packet carrying the upper layer session identified by above 4fields, Src_IP add, Dst_IP add, Src_UDP_Port and Dst_UDP_Port, has anSID field in its optional header. When the value of this field is set to0, the link layer packet carrying the upper layer session may not havean SID field in its optional header. When the value of this field is setto 1, the link layer packet carrying the upper layer session can have anSID field in its optional header and the value the SID field can be sameas the following SID field in this table.

compressed_flag can be a 1-bit Boolean field that indicates whether theheader compression is applied the link layer packets carrying the upperlayer session identified by above 4 fields, Src_IP_add, Dst_IP_add,Src_UDP_Port and Dst_UDP_Port. When the value of this field is set to 0,the link layer packet carrying the upper layer session may have a valueof 0x00 of Packet_Type field in its base header. When the value of thisfield is set to 1, the link layer packet carrying the upper layersession may have a value of 0x01 of Packet_Type field in its base headerand the Context_ID field can be present.

SID can be an 8-bit unsigned integer field that indicates sub streamidentifier for the link layer packets carrying the upper layer sessionidentified by above 4 fields, Src_IP_add, Dst_IP_add, Src_UDP_Port andDst_UDP_Port. This field can be present when the value of SID_flag isequal to 1.

context id can be an 8-bit field that provides a reference for thecontext id (CID) provided in the ROHC-U description table. This fieldcan be present when the value of compressed_flag is equal to 1.

An example of the RoHC-U description table (tsib14020) according to thepresent invention is illustrated. As described in the foregoing, theRoHC-U adaptation module may generate information related to headercompression.

signaling_type can be an 8-bit field that indicates the type ofsignaling carried by this table. The value of signaling_type field forROHC-U description table (RDT) can be set to “0x02”.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

context_id can be an 8-bit field that indicates the context id (CID) ofthe compressed IP stream. In this system, 8-bit CID can be used forlarge CID.

context_profile can be an 8-bit field that indicates the range ofprotocols used to compress the stream. This field can be omitted.

adaptation_mode can be a 2-bit field that indicates the mode ofadaptation module in this PLP. Adaptation modes have been describedabove.

context_config can be a 2-bit field that indicates the combination ofthe context information. If there is no context information in thistable, this field may be set to “0x0”. If the static_chain( ) ordynamic_chain( ) byte is included in this table, this field may be setto “0x01” or “0x02” respectively. If both of the static_chain( ) anddynamic_chain( ) byte are included in this table, this field may be setto “0x03”.

context_length can be an 8-bit field that indicates the length of thestatic chain byte sequence. This field can be omitted.

static_chain_byte ( ) can be a field that conveys the static informationused to initialize the ROHC-U decompressor. The size and structure ofthis field depend on the context profile.

dynamic_chain⁻byte ( ) can be a field that conveys the dynamicinformation used to initialize the ROHC-U decompressor. The size andstructure of this field depend on the context profile.

The static_chain_byte can be defined as sub-header information of IRpacket. The dynamic_chain_byte can be defined as sub-header informationof IR packet and IR-DYN packet.

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the transmitter side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead reduction part, and/or anencapsulation part. In addition, the link layer on the transmitter sidemay include a scheduler for controlling and scheduling an overalloperation of the link layer and/or input and output parts of the linklayer.

First, signaling information of an upper layer and/or a system parametertsib15010 may be delivered to the link layer. In addition, an IP streamincluding IP packets may be delivered to the link layer from an IP layertsib15110.

As described above, the scheduler tsib15020 may determine and controloperations of several modules included in the link layer. The deliveredsignaling information and/or system parameter tsib15010 may be faltereror used by the scheduler tsib15020. Information, which corresponds to apart of the delivered signaling information and/or system parametertsib15010, necessary for a receiver may be delivered to the link layersignaling part. In addition, information, which corresponds to a part ofthe signaling information, necessary for an operation of the link layermay be delivered to an overhead reduction controller tsib15120 or anencapsulation controller tsib15180.

The link layer signaling part may collect information to be transmittedas a signal in a physical layer, and convert/configure the informationin a form suitable for transmission. The link layer signaling part mayinclude a signaling manager tsib15030, a signaling formatter tsib15040,and/or a buffer for channels tsib15050.

The signaling manager tsib15030 may receive signaling informationdelivered from the scheduler tsib15020 and/or signaling (and/or context)information delivered from the overhead reduction part. The signalingmanager tsib15030 may determine a path for transmission of the signalinginformation for delivered data. The signaling information may bedelivered through the path determined by the signaling managertsib15030. As described in the foregoing, signaling information to betransmitted through a divided channel such as the FIC, the EAS, etc. maybe delivered to the signaling formatter tsib15040, and other signalinginformation may be delivered to an encapsulation buffer tsib15070.

The signaling formatter tsib15040 may format related signalinginformation in a form suitable for each divided channel such thatsignaling information may be transmitted through a separately dividedchannel. As described in the foregoing, the physical layer may includeseparate physically/logically divided channels. The divided channels maybe used to transmit FIC signaling information or EAS-relatedinformation. The FIC or EAS-related information may be sorted by thesignaling manager tsib15030, and input to the signaling formattertsib15040. The signaling formatter tsib15040 may format the informationbased on each separate channel. When the physical layer is designed totransmit particular signaling information through a separately dividedchannel other than the FIC and the EAS, a signaling formatter for theparticular signaling information may be additionally provided. Throughthis scheme, the link layer may be compatible with various physicallayers.

The buffer for channels tsib15050 may deliver the signaling informationreceived from the signaling formatter tsib15040 to separate dedicatedchannels tsib15060. The number and content of the separate channels mayvary depending on embodiments.

As described in the foregoing, the signaling manager tsib15030 maydeliver signaling information, which is not delivered to a particularchannel, to the encapsulation buffer tsib15070. The encapsulation buffertsib15070 may function as a buffer that receives the signalinginformation which is not delivered to the particular channel.

An encapsulation block for signaling information tsib15080 mayencapsulate the signaling information which is not delivered to theparticular channel. A transmission buffer tsib15090 may function as abuffer that delivers the encapsulated signaling information to a DP forsignaling information tsib15100. Here, the DP for signaling informationtsib15100 may refer to the above-described PLS region.

The overhead reduction part may allow efficient transmission by removingoverhead of packets delivered to the link layer. It is possible toconfigure overhead reduction parts corresponding to the number of IPstreams input to the link layer.

An overhead reduction buffer tsib15130 may receive an IP packetdelivered from an upper layer. The received IP packet may be input tothe overhead reduction part through the overhead reduction buffertsib15130.

An overhead reduction controller tsib15120 may determine whether toperform overhead reduction on a packet stream input to the overheadreduction buffer tsib15130. The overhead reduction controller tsib15120may determine whether to perform overhead reduction for each packetstream. When overhead reduction is performed on a packet stream, packetsmay be delivered to a robust header compression (RoHC) compressortsib15140 to perform overhead reduction. When overhead reduction is notperformed on a packet stream, packets may be delivered to theencapsulation part to perform encapsulation without overhead reduction.Whether to perform overhead reduction of packets may be determined basedon the signaling information tsib15010 delivered to the link layer. Thesignaling information may be delivered to the encapsulation controllertsib15180 by the scheduler tsib15020.

The RoHC compressor tsib15140 may perform overhead reduction on a packetstream. The RoHC compressor tsib15140 may perform an operation ofcompressing a header of a packet. Various schemes may be used foroverhead reduction. Overhead reduction may be performed using a schemeproposed by the present invention. The present invention presumes an IPstream, and thus an expression “RoHC compressor” is used. However, thename may be changed depending on embodiments. The operation is notrestricted to compression of the IP stream, and overhead reduction ofall types of packets may be performed by the RoHC compressor tsib15140.

A packet stream configuration block tsib15150 may separate informationto be transmitted to a signaling region and information to betransmitted to a packet stream from IP packets having compressedheaders. The information to be transmitted to the packet stream mayrefer to information to be transmitted to a DP region. The informationto be transmitted to the signaling region may be delivered to asignaling and/or context controller tsib15160. The information to betransmitted to the packet stream may be transmitted to the encapsulationpart.

The signaling and/or context controller tsib15160 may collect signalingand/or context information and deliver the signaling and/or contextinformation to the signaling manager in order to transmit the signalingand/or context information to the signaling region.

The encapsulation part may perform an operation of encapsulating packetsin a form suitable for a delivery to the physical layer. It is possibleto configure encapsulation parts corresponding to the number of IPstreams.

An encapsulation buffer tsib15170 may receive a packet stream forencapsulation. Packets subjected to overhead reduction may be receivedwhen overhead reduction is performed, and an input IP packet may bereceived without change when overhead reduction is not performed.

An encapsulation controller tsib15180 may determine whether toencapsulate an input packet stream. When encapsulation is performed, thepacket stream may be delivered to a segmentation/concatenation blocktsib15190. When encapsulation is not performed, the packet stream may bedelivered to a transmission buffer tsib15230. Whether to encapsulatepackets may be determined based on the signaling information tsib15010delivered to the link layer. The signaling information may be deliveredto the encapsulation controller tsib15180 by the scheduler tsib15020.

In the segmentation/concatenation block tsib15190, the above-describedsegmentation or concatenation operation may be performed on packets. Inother words, when an input IP packet is longer than a link layer packetcorresponding to an output of the link layer, one IP packet may besegmented into several segments to configure a plurality of link layerpacket payloads. On the other hand, when an input IP packet is shorterthan a link layer packet corresponding to an output of the link layer,several IP packets may be concatenated to configure one link layerpacket payload.

A packet configuration table tsib15200 may have configurationinformation of a segmented and/or concatenated link layer packet. Atransmitter and a receiver may have the same information in the packetconfiguration table tsib15200. The transmitter and the receiver mayrefer to the information of the packet configuration table tsib15200. Anindex value of the information of the packet configuration tabletsib15200 may be included in a header of the link layer packet.

A link layer header information block tsib15210 may collect headerinformation generated in an encapsulation process. In addition, the linklayer header information block tsib15210 may collect header informationincluded in the packet configuration table tsib15200. The link layerheader information block tsib15210 may configure header informationaccording to a header structure of the link layer packet.

A header attachment block tsib15220 may add a header to a payload of asegmented and/or concatenated link layer packet. The transmission buffertsib15230 may function as a buffer to deliver the link layer packet to aDP tsib15240 of the physical layer.

The respective blocks, modules, or parts may be configured as onemodule/protocol or a plurality of modules/protocols in the link layer.

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the receiver side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead processing part, and/or adecapsulation part. In addition, the link layer on the receiver side mayinclude a scheduler for controlling and scheduling overall operation ofthe link layer and/or input and output parts of the link layer.

First, information received through a physical layer may be delivered tothe link layer. The link layer may process the information, restore anoriginal state before being processed at a transmitter side, and thendeliver the information to an upper layer. In the present embodiment,the upper layer may be an IP layer.

Information, which is separated in the physical layer and deliveredthrough a particular channel tsib16030, may be delivered to a link layersignaling part. The link layer signaling part may determine signalinginformation received from the physical layer, and deliver the determinedsignaling information to each part of the link layer.

A buffer for channels tsib16040 may function as a buffer that receivessignaling information transmitted through particular channels. Asdescribed in the foregoing, when physically/logically divided separatechannels are present in the physical layer, it is possible to receivesignaling information transmitted through the channels. When theinformation received from the separate channels is segmented, thesegmented information may be stored until complete information isconfigured.

A signaling decoder/parser tsib16050 may verify a format of thesignaling information received through the particular channel, andextract information to be used in the link layer. When the signalinginformation received through the particular channel is encoded, decodingmay be performed. In addition, according to a given embodiment, it ispossible to verify integrity, etc. of the signaling information.

A signaling manager tsib16060 may integrate signaling informationreceived through several paths. Signaling information received through aDP for signaling tsib16070 to be described below may be integrated inthe signaling manager tsib16060. The signaling manager tsib16060 maydeliver signaling information necessary for each part in the link layer.For example, the signaling manager tsib16060 may deliver contextinformation, etc. for recovery of a packet to the overhead processingpart. In addition, the signaling manager tsib16060 may deliver signalinginformation for control to a scheduler tsib16020.

General signaling information, which is not received through a separateparticular channel, may be received through the DP for signalingtsib16070. Here, the DP for signaling may refer to PLS, L1, etc. Here,the DP may be referred to as a PLP. A reception buffer tsib16080 mayfunction as a buffer that receives signaling information delivered fromthe DP for signaling. In a decapsulation block for signaling informationtsib16090, the received signaling information may be decapsulated. Thedecapsulated signaling information may be delivered to the signalingmanager tsib16060 through a decapsulation buffer tsib16100. As describedin the foregoing, the signaling manager tsib16060 may collate signalinginformation, and deliver the collated signaling information to anecessary part in the link layer.

The scheduler tsib16020 may determine and control operations of severalmodules included in the link layer. The scheduler tsib16020 may controleach part of the link layer using receiver information tsib16010 and/orinformation delivered from the signaling manager tsib16060. In addition,the scheduler tsib16020 may determine an operation mode, etc. of eachpart. Here, the receiver information tsib16010 may refer to informationpreviously stored in the receiver. The scheduler tsib16020 may useinformation changed by a user such as channel switching, etc. to performa control operation.

The decapsulation part may filter a packet received from a DP tsib16110of the physical layer, and separate a packet according to a type of thepacket. It is possible to configure decapsulation parts corresponding tothe number of DPs that can be simultaneously decoded in the physicallayer.

The decapsulation buffer tsib16100 may function as a buffer thatreceives a packet stream from the physical layer to performdecapsulation. A decapsulation controller tsib16130 may determinewhether to decapsulate an input packet stream. When decapsulation isperformed, the packet stream may be delivered to a link layer headerparser tsib16140. When decapsulation is not performed, the packet streammay be delivered to an output buffer tsib16220. The signalinginformation received from the scheduler tsib16020 may be used todetermine whether to perform decapsulation.

The link layer header parser tsib16140 may identify a header of thedelivered link layer packet. It is possible to identify a configurationof an IP packet included in a payload of the link layer packet byidentifying the header. For example, the IP packet may be segmented orconcatenated.

A packet configuration table tsib16150 may include payload informationof segmented and/or concatenated link layer packets. The transmitter andthe receiver may have the same information in the packet configurationtable tsib16150. The transmitter and the receiver may refer to theinformation of the packet configuration table tsib16150. It is possibleto find a value necessary for reassembly based on index informationincluded in the link layer packet.

A reassembly block tsib16160 may configure payloads of the segmentedand/or concatenated link layer packets as packets of an original IPstream. Segments may be collected and reconfigured as one IP packet, orconcatenated packets may be separated and reconfigured as a plurality ofIP packet streams. Recombined IP packets may be delivered to theoverhead processing part.

The overhead processing part may perform an operation of restoring apacket subjected to overhead reduction to an original packet as areverse operation of overhead reduction performed in the transmitter.This operation may be referred to as overhead processing. It is possibleto configure overhead processing parts corresponding to the number ofDPs that can be simultaneously decoded in the physical layer.

A packet recovery buffer tsib16170 may function as a buffer thatreceives a decapsulated RoHC packet or IP packet to perform overheadprocessing.

An overhead controller tsib16180 may determine whether to recover and/ordecompress the decapsulated packet. When recovery and/or decompressionare performed, the packet may be delivered to a packet stream recoveryblock tsib16190. When recovery and/or decompression are not performed,the packet may be delivered to the output buffer tsib16220. Whether toperform recovery and/or decompression may be determined based on thesignaling information delivered by the scheduler tsib16020.

The packet stream recovery block tsib16190 may perform an operation ofintegrating a packet stream separated from the transmitter with contextinformation of the packet stream. This operation may be a process ofrestoring a packet stream such that an RoHC decompressor tsib16210 canperform processing. In this process, it is possible to receive signalinginformation and/or context information from a signaling and/or contextcontroller tsib16200. The signaling and/or context controller tsib16200may determine signaling information delivered from the transmitter, anddeliver the signaling information to the packet stream recovery blocktsib16190 such that the signaling information may be mapped to a streamcorresponding to a context ID.

The RoHC decompressor tsib16210 may restore headers of packets of thepacket stream. The packets of the packet stream may be restored to formsof original IP packets through restoration of the headers. In otherwords, the RoHC decompressor tsib16210 may perform overhead processing.

The output buffer tsib16220 may function as a buffer before an outputstream is delivered to an IP layer tsib16230.

The link layers of the transmitter and the receiver proposed in thepresent invention may include the blocks or modules described above. Inthis way, the link layer may independently operate irrespective of anupper layer and a lower layer, overhead reduction may be efficientlyperformed, and a supportable function according to an upper/lower layermay be easily defined/added/deleted.

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides).

In the present invention, a plurality of service providers(broadcasters) may provide services within one frequency band. Inaddition, a service provider may provide a plurality of services, andone service may include one or more components. It can be consideredthat the user receives content using a service as a unit.

The present invention presumes that a transmission protocol based on aplurality of sessions is used to support an IP hybrid broadcast.Signaling information delivered through a signaling path may bedetermined based on a transmission configuration of each protocol.Various names may be applied to respective protocols according to agiven embodiment.

In the illustrated data configuration tsib17010 on the transmittingside, service providers (broadcasters) may provide a plurality ofservices (Service #1, #2, . . . ). In general, a signal for a servicemay be transmitted through a general transmission session (signaling C).However, the signal may be transmitted through a particular session(dedicated session) according to a given embodiment (signaling B).

Service data and service signaling information may be encapsulatedaccording to a transmission protocol. According to a given embodiment,an IP/UDP layer may be used. According to a given embodiment, a signalin the IP/UDP layer (signaling A) may be additionally provided. Thissignaling may be omitted.

Data processed using the IP/UDP may be input to the link layer. Asdescribed in the foregoing, overhead reduction and/or encapsulation maybe performed in the link layer. Here, link layer signaling may beadditionally provided. Link layer signaling may include a systemparameter, etc. Link layer signaling has been described above.

The service data and the signaling information subjected to the aboveprocess may be processed through PLPs in a physical layer. Here, a PLPmay be referred to as a DP. The example illustrated in the figurepresumes a case in which a base DP/PLP is used. However, depending onembodiments, transmission may be performed using only a general DP/PLPwithout the base DP/PLP.

In the example illustrated in the figure, a particular channel(dedicated channel) such as an FIC, an EAC, etc. is used. A signaldelivered through the FIC may be referred to as a fast information table(FIT), and a signal delivered through the EAC may be referred to as anemergency alert table (EAT). The FIT may be identical to theabove-described SLT. The particular channels may not be used dependingon embodiments. When the particular channel (dedicated channel) is notconfigured, the FIT and the EAT may be transmitted using a general linklayer signaling transmission scheme, or transmitted using a PLP via theIP/UDP as other service data.

According to a given embodiment, system parameters may include atransmitter-related parameter, a service provider-related parameter,etc. Link layer signaling may include IP header compression-relatedcontext information and/or identification information of data to whichthe context is applied. Signaling of an upper layer may include an IPaddress, a UDP number, service/component information, emergencyalert-related information, an IP/UDP address for service signaling, asession ID, etc. Detailed examples thereof have been described above.

In the illustrated data configuration tsib17020 on the receiving side,the receiver may decode only a PLP for a corresponding service usingsignaling information without having to decode all PLPs.

First, when the user selects or changes a service desired to bereceived, the receiver may be tuned to a corresponding frequency and mayread receiver information related to a corresponding channel stored in aDB, etc. The information stored in the DB, etc. of the receiver may beconfigured by reading an SLT at the time of initial channel scan.

After receiving the SLT and the information about the correspondingchannel, information previously stored in the DB is updated, andinformation about a transmission path of the service selected by theuser and information about a path, through which component informationis acquired or a signal necessary to acquire the information istransmitted, are acquired. When the information is not determined to bechanged using version information of the SLT, decoding or parsing may beomitted.

The receiver may verify whether SLT information is included in a PLP byparsing physical signaling of the PLP in a corresponding broadcaststream (not illustrated), which may be indicated through a particularfield of physical signaling. It is possible to access a position atwhich a service layer signal of a particular service is transmitted byaccessing the SLT information. The service layer signal may beencapsulated into the IP/UDP and delivered through a transmissionsession. It is possible to acquire information about a componentincluded in the service using this service layer signaling. A specificSLT-SLS configuration is as described above.

In other words, it is possible to acquire transmission path information,for receiving upper layer signaling information (service signalinginformation) necessary to receive the service, corresponding to one ofseveral packet streams and PLPs currently transmitted on a channel usingthe SLT. The transmission path information may include an IP address, aUDP port number, a session ID, a PLP ID, etc. Here, depending onembodiments, a value previously designated by the IANA or a system maybe used as an IP/UDP address. The information may be acquired using ascheme of accessing a DB or a shared memory, etc.

When the link layer signal and service data are transmitted through thesame PLP, or only one PLP is operated, service data delivered throughthe PLP may be temporarily stored in a device such as a buffer, etc.while the link layer signal is decoded.

It is possible to acquire information about a path through which theservice is actually transmitted using service signaling information of aservice to be received. In addition, a received packet stream may besubjected to decapsulation and header recovery using information such asoverhead reduction for a PLP to be received, etc.

In the illustrated example (tsib17020), the FIC and the EAC are used,and a concept of the base DP/PLP is presumed. As described in theforegoing, concepts of the FIC, the EAC, and the base DP/PLP may not beused.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas. The present invention proposes a physical profile (orsystem) optimized to minimize receiver complexity while attaining theperformance required for a particular use case. Physical (PHY) profiles(base, handheld and advanced profiles) according to an embodiment of thepresent invention are subsets of all configurations that a correspondingreceiver should implement. The PHY profiles share most of the functionalblocks but differ slightly in specific blocks and/or parameters. For thesystem evolution, future profiles may also be multiplexed with existingprofiles in a single radio frequency (RF) channel through a futureextension frame (FEF). The base profile and the handheld profileaccording to the embodiment of the present invention refer to profilesto which MIMO is not applied, and the advanced profile refers to aprofile to which MIMO is applied. The base profile may be used as aprofile for both the terrestrial broadcast service and the mobilebroadcast service. That is, the base profile may be used to define aconcept of a profile which includes the mobile profile. In addition, theadvanced profile may be divided into an advanced profile for a baseprofile with MIMO and an advanced profile for a handheld profile withMIMO. Moreover, the profiles may be changed according to intention ofthe designer.

The following terms and definitions may be applied to the presentinvention. The following terms and definitions may be changed accordingto design.

Auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators.

Base data pipe: data pipe that carries service signaling data.

Baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding).

Cell: modulation value that is carried by one carrier of orthogonalfrequency division multiplexing (OFDM) transmission.

Coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data.

Data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or a plurality ofservice(s) or service component(s).

Data pipe unit (DPU): a basic unit for allocating data cells to a DP ina frame.

Data symbol: OFDM symbol in a frame which is not a preamble symbol (thedata symbol encompasses the frame signaling symbol and frame edgesymbol).

DP_ID: this 8-bit field identifies uniquely a DP within the systemidentified by the SYSTEM_ID.

Dummy cell: cell carrying a pseudo-random value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams.

Emergency alert channel (EAC): part of a frame that carries EASinformation data.

Frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol.

Frame repetition unit: a set of frames belonging to the same ordifferent physical layer profiles including an FEF, which is repeatedeight times in a superframe.

Fast information channel (FIC): a logical channel in a frame thatcarries mapping information between a service and the corresponding baseDP.

FECBLOCK: set of LDPC-encoded bits of DP data.

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of an elementary period T.

Frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot pattern, which carries a part of the PLS data.

Frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern.

Frame group: the set of all frames having the same PHY profile type in asuperframe.

Future extension frame: physical layer time slot within the superframethat may be used for future extension, which starts with a preamble.

Futurecast UTB system: proposed physical layer broadcast system, theinput of which is one or more MPEG2-TS, IP or general stream(s) and theoutput of which is an RF signal.

Input stream: a stream of data for an ensemble of services delivered tothe end users by the system.

Normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol.

PHY profile: subset of all configurations that a corresponding receivershould implement.

PLS: physical layer signaling data including PLS1 and PLS2.

PLS1: a first set of PLS data carried in a frame signaling symbol (FSS)having a fixed size, coding and modulation, which carries basicinformation about a system as well as parameters needed to decode PLS2.

NOTE: PLS1 data remains constant for the duration of a frame group.

PLS2: a second set of PLS data transmitted in the FSS, which carriesmore detailed PLS data about the system and the DPs.

PLS2 dynamic data: PLS2 data that dynamically changes frame-by-frame.

PLS2 static data: PLS2 data that remains static for the duration of aframe group.

Preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system.

Preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located at the beginning of a frame.

The preamble symbol is mainly used for fast initial band scan to detectthe system signal, timing thereof, frequency offset, and FFT size.

Reserved for future use: not defined by the present document but may bedefined in future.

Superframe: set of eight frame repetition units.

Time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of a timeinterleaver memory.

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs.

NOTE: The TI group may be mapped directly to one frame or may be mappedto a plurality of frames. The TI group may contain one or more TIblocks.

Type 1 DP: DP of a frame where all DPs are mapped to the frame in timedivision multiplexing (TDM) scheme.

Type 2 DP: DP of a frame where all DPs are mapped to the frame infrequency division multiplexing (FDM) scheme.

XFECBLOCK: set of N_(cells) cells carrying all the bits of one LDPCFECBLOCK.

FIG. 18 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal transmission apparatus for future broadcastservices according to the present embodiment may include an inputformatting block 1000, a bit interleaved coding & modulation (BICM)block 1010, a frame building block 1020, an OFDM generation block 1030and a signaling generation block 1040. Description will be given of anoperation of each block of the broadcast signal transmission apparatus.

In input data according to an embodiment of the present invention, IPstream/packets and MPEG2-TS may be main input formats, and other streamtypes are handled as general streams. In addition to these data inputs,management information is input to control scheduling and allocation ofthe corresponding bandwidth for each input stream. In addition, thepresent invention allows simultaneous input of one or a plurality of TSstreams, IP stream(s) and/or a general stream(s).

The input formatting block 1000 may demultiplex each input stream intoone or a plurality of data pipes, to each of which independent codingand modulation are applied. A DP is the basic unit for robustnesscontrol, which affects QoS. One or a plurality of services or servicecomponents may be carried by one DP. The DP is a logical channel in aphysical layer for delivering service data or related metadata capableof carrying one or a plurality of services or service components.

In addition, a DPU is a basic unit for allocating data cells to a DP inone frame.

An input to the physical layer may include one or a plurality of datastreams. Each of the data streams is delivered by one DP. The inputformatting block 1000 may covert a data stream input through one or morephysical paths (or DPs) into a baseband frame (BBF). In this case, theinput formatting block 1000 may perform null packet deletion or headercompression on input data (a TS or IP input stream) in order to enhancetransmission efficiency. A receiver may have a priori information for aparticular part of a header, and thus this known information may bedeleted from a transmitter. A null packet deletion block 3030 may beused only for a TS input stream.

In the BICM block 1010, parity data is added for error correction andencoded bit streams are mapped to complex-value constellation symbols.The symbols are interleaved across a specific interleaving depth that isused for the corresponding DP. For the advanced profile, MIMO encodingis performed in the BICM block 1010 and an additional data path is addedat the output for MIMO transmission.

The frame building block 1020 may map the data cells of the input DPsinto the OFDM symbols within a frame, and perform frequency interleavingfor frequency-domain diversity, especially to combat frequency-selectivefading channels. The frame building block 1020 may include a delaycompensation block, a cell mapper and a frequency interleaver.

The delay compensation block may adjust timing between DPs andcorresponding PLS data to ensure that the DPs and the corresponding PLSdata are co-timed at a transmitter side. The PLS data is delayed by thesame amount as the data pipes by addressing the delays of data pipescaused by the input formatting block and BICM block. The delay of theBICM block is mainly due to the time interleaver. In-band signaling datacarries information of the next TI group so that the information iscarried one frame ahead of the DPs to be signaled. The delaycompensation block delays in-band signaling data accordingly.

The cell mapper may map PLS, DPs, auxiliary streams, dummy cells, etc.to active carriers of the OFDM symbols in the frame. The basic functionof the cell mapper 7010 is to map data cells produced by the TIs foreach of the DPs, PLS cells, and EAC/FIC cells, if any, into arrays ofactive OFDM cells corresponding to each of the OFDM symbols within aframe. A basic function of the cell mapper is to map a data cellgenerated by time interleaving for each DP and PLS cell to an array ofactive OFDM cells (if present) corresponding to respective OFDM symbolsin one frame. Service signaling data (such as program specificinformation (PSI)/SI) may be separately gathered and sent by a DP. Thecell mapper operates according to dynamic information produced by ascheduler and the configuration of a frame structure. The frequencyinterleaver may randomly interleave data cells received from the cellmapper to provide frequency diversity. In addition, the frequencyinterleaver may operate on an OFDM symbol pair including two sequentialOFDM symbols using a different interleaving-seed order to obtain maximuminterleaving gain in a single frame.

The OFDM generation block 1030 modulates OFDM carriers by cells producedby the frame building block, inserts pilots, and produces a time domainsignal for transmission. In addition, this block subsequently insertsguard intervals, and applies peak-to-average power ratio (PAPR)reduction processing to produce a final RF signal.

Specifically, after inserting a preamble at the beginning of each frame,the OFDM generation block 1030 may apply conventional OFDM modulationhaving a cyclic prefix as a guard interval. For antenna space diversity,a distributed MISO scheme is applied across transmitters. In addition, aPAPR scheme is performed in the time domain. For flexible networkplanning, the present invention provides a set of various FFT sizes,guard interval lengths and corresponding pilot patterns.

In addition, the present invention may multiplex signals of a pluralityof broadcast transmission/reception systems in the time domain such thatdata of two or more different broadcast transmission/reception systemsproviding broadcast services may be simultaneously transmitted in thesame RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc.

The signaling generation block 1040 may create physical layer signalinginformation used for an operation of each functional block. Thissignaling information is also transmitted so that services of interestare properly recovered at a receiver side. Signaling informationaccording to an embodiment of the present invention may include PLSdata. PLS provides the receiver with a means to access physical layerDPs. The PLS data includes PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in an FSS symbol in aframe having a fixed size, coding and modulation, which carries basicinformation about the system in addition to the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable reception anddecoding of the PLS2 data. In addition, the PLS1 data remains constantfor the duration of a frame group.

The PLS2 data is a second set of PLS data transmitted in an FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode a desired DP. The PLS2 signaling further includes twotypes of parameters, PLS2 static data (PLS2-STAT data) and PLS2 dynamicdata (PLS2-DYN data). The PLS2 static data is PLS2 data that remainsstatic for the duration of a frame group and the PLS2 dynamic data isPLS2 data that dynamically changes frame by frame. Details of the PLSdata will be described later.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 19 illustrates a BICM block according to an embodiment of thepresent invention.

The BICM block illustrated in FIG. 19 corresponds to an embodiment ofthe BICM block 1010 described with reference to FIG. 18.

As described above, the broadcast signal transmission apparatus forfuture broadcast services according to the embodiment of the presentinvention may provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS depends on characteristics of a service provided by thebroadcast signal transmission apparatus for future broadcast servicesaccording to the embodiment of the present invention, data correspondingto respective services needs to be processed using different schemes.Accordingly, the BICM block according to the embodiment of the presentinvention may independently process respective DPs by independentlyapplying SISO, MISO and MIMO schemes to data pipes respectivelycorresponding to data paths. Consequently, the broadcast signaltransmission apparatus for future broadcast services according to theembodiment of the present invention may control QoS for each service orservice component transmitted through each DP.

(a) shows a BICM block applied to a profile (or system) to which MIMO isnot applied, and (b) shows a BICM block of a profile (or system) towhich MIMO is applied.

The BICM block to which MIMO is not applied and the BICM block to whichMIMO is applied may include a plurality of processing blocks forprocessing each DP.

Description will be given of each processing block of the BICM block towhich MIMO is not applied and the BICM block to which MIMO is applied.

A processing block 5000 of the BICM block to which MIMO is not appliedmay include a data FEC encoder 5010, a bit interleaver 5020, aconstellation mapper 5030, a signal space diversity (SSD) encoding block5040 and a time interleaver 5050.

The data FEC encoder 5010 performs FEC encoding on an input BBF togenerate FECBLOCK procedure using outer coding (BCH) and inner coding(LDPC). The outer coding (BCH) is optional coding method. A detailedoperation of the data FEC encoder 5010 will be described later.

The bit interleaver 5020 may interleave outputs of the data FEC encoder5010 to achieve optimized performance with a combination of LDPC codesand a modulation scheme while providing an efficiently implementablestructure. A detailed operation of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 may modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or each cellword from the cell-word demultiplexer 5010-1 in the advanced profileusing either QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, orNUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, orNUC-1024) mapping to give a power-normalized constellation point, e₁.This constellation mapping is applied only for DPs. It is observed thatQAM-16 and NUQs are square shaped, while NUCs have arbitrary shapes.When each constellation is rotated by any multiple of 90 degrees, therotated constellation exactly overlaps with its original one. This“rotation-sense” symmetric property makes the capacities and the averagepowers of the real and imaginary components equal to each other. BothNUQs and NUCs are defined specifically for each code rate and theparticular one used is signaled by the parameter DP_MOD filed in thePLS2 data.

The time interleaver 5050 may operates at a DP level. Parameters of timeinterleaving (TI) may be set differently for each DP. A detailedoperation of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block to which MIMO is applied mayinclude the data FEC encoder, the bit interleaver, the constellationmapper, and the time interleaver.

However, the processing block 5000-1 is distinguished from theprocessing block 5000 of the BICM block to which MIMO is not applied inthat the processing block 5000-1 further includes a cell-worddemultiplexer 5010-1 and a MIMO encoding block 5020-1.

In addition, operations of the data FEC encoder, the bit interleaver,the constellation mapper, and the time interleaver in the processingblock 5000-1 correspond to those of the data FEC encoder 5010, the bitinterleaver 5020, the constellation mapper 5030, and the timeinterleaver 5050 described above, and thus description thereof isomitted.

The cell-word demultiplexer 5010-1 is used for a DP of the advancedprofile to divide a single cell-word stream into dual cell-word streamsfor MIMO processing.

The MIMO encoding block 5020-1 may process an output of the cell-worddemultiplexer 5010-1 using a MIMO encoding scheme. The MIMO encodingscheme is optimized for broadcast signal transmission. MIMO technologyis a promising way to obtain a capacity increase but depends on channelcharacteristics. Especially for broadcasting, a strong LOS component ofa channel or a difference in received signal power between two antennascaused by different signal propagation characteristics makes itdifficult to obtain capacity gain from MIMO. The proposed MIMO encodingscheme overcomes this problem using rotation-based precoding and phaserandomization of one of MIMO output signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. A MIMO encoding modeof the present invention may be defined as full-rate spatialmultiplexing (FR-SM). FR-SM encoding may provide capacity increase withrelatively small complexity increase at the receiver side. In addition,the MIMO encoding scheme of the present invention has no restriction onan antenna polarity configuration.

MIMO processing is applied at the DP level. NUQ (e_(1,i) and e_(2,i))corresponding to a pair of constellation mapper outputs is fed to aninput of a MIMO encoder. Paired MIMO encoder output (g1,i and g2,i) istransmitted by the same carrier k and OFDM symbol 1 of respective TXantennas thereof.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 20 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 20 corresponds to another embodimentof the BICM block 1010 described with reference to FIG. 18.

FIG. 20 illustrates a BICM block for protection of physical layersignaling (PLS), an emergency alert channel (EAC) and a fast informationchannel (FIC). The EAC is a part of a frame that carries EAS informationdata, and the FIC is a logical channel in a frame that carries mappinginformation between a service and a corresponding base DP. Details ofthe EAC and FIC will be described later.

Referring to FIG. 20, the BICM block for protection of the PLS, the EACand the FIC may include a PLS FEC encoder 6000, a bit interleaver 6010and a constellation mapper 6020.

In addition, the PLS FEC encoder 6000 may include a scrambler, a BCHencoding/zero insertion block, an LDPC encoding block and an LDPC paritypuncturing block. Description will be given of each block of the BICMblock.

The PLS FEC encoder 6000 may encode scrambled PLS 1/2 data, EAC and FICsections.

The scrambler may scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block may perform outer encoding on thescrambled PLS 1/2 data using a shortened BCH code for PLS protection,and insert zero bits after BCH encoding. For PLS1 data only, output bitsof zero insertion may be permutted before LDPC encoding.

The LDPC encoding block may encode an output of the BCH encoding/zeroinsertion block using an LDPC code. To generate a complete coded block,C_(ldpc) and parity bits P_(ldpc) are encoded systematically from eachzero-inserted PLS information block I_(ldpc) and appended thereto.

C _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ , i ₁ , . . . , i _(K) _(ldpc) ⁻¹, p ₀ , p ₁ , . . . , p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 1]

The LDPC parity puncturing block may perform puncturing on the PLS1 dataand the PLS2 data.

When shortening is applied to PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. In addition, for PLS2 dataprotection, LDPC parity bits of PLS2 are punctured after LDPC encoding.These punctured bits are not transmitted.

The bit interleaver 6010 may interleave each of shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 may map the bit-ineterleaved PLS1 data andPLS2 data to constellations.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 21 illustrates a bit interleaving process of PLS according to anembodiment of the present invention.

Each shortened and punctured PLS1 and PLS2 coded block is interleavedbit-by-bit as described in FIG. 22. Each block of additional parity bitsis interleaved with the same block interleaving structure butseparately.

In the case of BPSK, there are two branches for bit interleaving toduplicate FEC coded bits in the real and imaginary parts. Each codedblock is written to the upper branch first. The bits are mapped to thelower branch by applying modulo N_(FEC) addition with cyclic shiftingvalue floor (N_(FEC)/2), where N_(FEC) is the length of each LDPC codedblock after shortening and puncturing.

In other modulation cases, such as QSPK, QAM-16 and NUQ-64, FEC codedbits are written serially into the interleaver column-wise, where thenumber of columns is the same as the modulation order.

In the read operation, the bits for one constellation symbol are readout sequentially row-wise and fed into the bit demultiplexer block.These operations are continued until the end of the column.

Each bit interleaved group is demultiplexed bit-by-bit in a group beforeconstellation mapping. Depending on modulation order, there are twomapping rules. In the case of BPSK and QPSK, the reliability of bits ina symbol is equal. Therefore, the bit group read out from the bitinterleaving block is mapped to a QAM symbol without any operation.

In the cases of QAM-16 and NUQ-64 mapped to a QAM symbol, the rule ofoperation is described in FIG. 23(a). As shown in FIG. 23(a), i is bitgroup index corresponding to column index in bit interleaving.

FIG. 21 shows the bit demultiplexing rule for QAM-16. This operationcontinues until all bit groups are read from the bit interleaving block.

FIG. 22 illustrates a configuration of a broadcast signal receptionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may correspond tothe broadcast signal transmission apparatus for future broadcastservices described with reference to FIG. 18.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may include asynchronization & demodulation module 9000, a frame parsing module 9010,a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the broadcast signal reception apparatus.

The synchronization & demodulation module 9000 may receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the broadcast signal receptionapparatus, and carry out demodulation corresponding to a reverseprocedure of a procedure performed by the broadcast signal transmissionapparatus.

The frame parsing module 9010 may parse input signal frames and extractdata through which a service selected by a user is transmitted. If thebroadcast signal transmission apparatus performs interleaving, the frameparsing module 9010 may carry out deinterleaving corresponding to areverse procedure of interleaving. In this case, positions of a signaland data that need to be extracted may be obtained by decoding dataoutput from the signaling decoding module 9040 to restore schedulinginformation generated by the broadcast signal transmission apparatus.

The demapping & decoding module 9020 may convert input signals into bitdomain data and then deinterleave the same as necessary. The demapping &decoding module 9020 may perform demapping of mapping applied fortransmission efficiency and correct an error generated on a transmissionchannel through decoding. In this case, the demapping & decoding module9020 may obtain transmission parameters necessary for demapping anddecoding by decoding data output from the signaling decoding module9040.

The output processor 9030 may perform reverse procedures of variouscompression/signal processing procedures which are applied by thebroadcast signal transmission apparatus to improve transmissionefficiency. In this case, the output processor 9030 may acquirenecessary control information from data output from the signalingdecoding module 9040. An output of the output processor 9030 correspondsto a signal input to the broadcast signal transmission apparatus and maybe MPEG-TSs, IP streams (v4 or v6) and generic streams.

The signaling decoding module 9040 may obtain PLS information from asignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9010, the demapping & decodingmodule 9020 and the output processor 9030 may execute functions thereofusing data output from the signaling decoding module 9040.

A frame according to an embodiment of the present invention is furtherdivided into a number of OFDM symbols and a preamble. As shown in (d),the frame includes a preamble, one or more frame signaling symbols(FSSs), normal data symbols and a frame edge symbol (FES).

The preamble is a special symbol that enables fast futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of a signal. Details of thepreamble will be described later.

A main purpose of the FSS is to carry PLS data. For fast synchronizationand channel estimation, and hence fast decoding of PLS data, the FSS hasa dense pilot pattern than a normal data symbol. The FES has exactly thesame pilots as the FSS, which enables frequency-only interpolationwithin the FES and temporal interpolation, without extrapolation, forsymbols immediately preceding the FES.

FIG. 23 illustrates a signaling hierarchy structure of a frame accordingto an embodiment of the present invention.

FIG. 23 illustrates the signaling hierarchy structure, which is splitinto three main parts corresponding to preamble signaling data 11000,PLS1 data 11010 and PLS2 data 11020. A purpose of a preamble, which iscarried by a preamble symbol in every frame, is to indicate atransmission type and basic transmission parameters of the frame. PLS1enables the receiver to access and decode the PLS2 data, which containsthe parameters to access a DP of interest. PLS2 is carried in everyframe and split into two main parts corresponding to PLS2-STAT data andPLS2-DYN data. Static and dynamic portions of PLS2 data are followed bypadding, if necessary.

Preamble signaling data according to an embodiment of the presentinvention carries 21 bits of information that are needed to enable thereceiver to access PLS data and trace DPs within the frame structure.Details of the preamble signaling data are as follows.

FFT_SIZE: This 2-bit field indicates an FFT size of a current framewithin a frame group as described in the following Table 1.

TABLE 1 Value FFT size 00  8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3-bit field indicates a guard interval fraction valuein a current superframe as described in the following Table 2.

TABLE 2 Value GI_FRACTION 000 ⅕ 001 1/10 010 1/20 011 1/40 100 1/80 1011/160 110 to 111 Reserved

EAC_FLAG: This 1-bit field indicates whether the EAC is provided in acurrent frame. If this field is set to ‘1’, an emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, theEAS is not carried in the current frame. This field may be switcheddynamically within a superframe.

PILOT_MODE: This 1-bit field indicates whether a pilot mode is a mobilemode or a fixed mode for a current frame in a current frame group. Ifthis field is set to ‘0’, the mobile pilot mode is used. If the field isset to ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used fora current frame in a current frame group. If this field is set to avalue of ‘1’, tone reservation is used for PAPR reduction. If this fieldis set to a value of ‘0’, PAPR reduction is not used.

RESERVED: This 7-bit field is reserved for future use.

FIG. 24 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable reception and decoding of PLS2. As mentioned above,the PLS1 data remain unchanged for the entire duration of one framegroup. A detailed definition of the signaling fields of the PLS1 data isas follows.

PREAMBLE_DATA: This 20-bit field is a copy of preamble signaling dataexcluding EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates a format of payload datacarried in a frame group. PAYLOAD_TYPE is signaled as shown in Table 3.

TABLE 3 Value Payload type 1XX TS is transmitted. X1X IP stream istransmitted. XX1 GS is transmitted.

NUM_FSS: This 2-bit field indicates the number of FSSs in a currentframe.

SYSTEM_VERSION: This 8-bit field indicates a version of a transmittedsignal format. SYSTEM_VERSION is divided into two 4-bit fields: a majorversion and a minor version.

Major version: The MSB corresponding to four bits of the SYSTEM_VERSIONfield indicates major version information. A change in the major versionfield indicates a non-backward-compatible change. A default value is‘0000’. For a version described in this standard, a value is set to‘0000’.

Minor version: The LSB corresponding to four bits of SYSTEM_VERSIONfield indicates minor version information. A change in the minor versionfield is backwards compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may include one ormore frequencies depending on the number of frequencies used perfuturecast UTB system. If a value of CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies a currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the futurecast UTBsystem within the ATSC network. The futurecast UTB system is aterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same futurecastUTB system may carry different input streams and use different RFs indifferent geographical areas, allowing local service insertion. Theframe structure and scheduling are controlled in one place and areidentical for all transmissions within the futurecast UTB system. One ormore futurecast UTB systems may have the same SYSTEM_ID meaning thatthey all have the same physical layer structure and configuration.

The following loop includes FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate an FRUconfiguration and a length of each frame type. A loop size is fixed sothat four PHY profiles (including an FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, unused fields are filled with zeros.

FRU_PHY_PROFILE: This 3-bit field indicates a PHY profile type of an(i+1)^(th) (i is a loop index) frame of an associated FRU. This fielduses the same signaling format as shown in Table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates a length of an (i+1)^(th)frame of an associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, an exact value of a frame duration may be obtained.

FRU_GI_FRACTION: This 3-bit field indicates a guard interval fractionvalue of an (i+1)^(th) frame of an associated FRU. FRU_GI_FRACTION issignaled according to Table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates an FEC type used by PLS2protection. The FEC type is signaled according to Table 4. Details ofLDPC codes will be described later.

TABLE 4 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01 to 11Reserved

PLS2_MOD: This 3-bit field indicates a modulation type used by PLS2. Themodulation type is signaled according to Table 5.

TABLE 5 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100 to111 Reserved

PLS2_SIZE_CELL: This 15-bit field indicates C_(total) _(_) _(partial)_(_) _(block), a size (specified as the number of QAM cells) of thecollection of full coded blocks for PLS2 that is carried in a currentframe group. This value is constant during the entire duration of thecurrent frame group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-STAT for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-DYN for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_REP_FLAG: This 1-bit flag indicates whether a PLS2 repetition modeis used in a current frame group. When this field is set to a value of‘1’, the PLS2 repetition mode is activated. When this field is set to avalue of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates C_(total) _(_)_(partial) _(_) _(block), a size (specified as the number of QAM cells)of the collection of partial coded blocks for PLS2 carried in everyframe of a current frame group, when PLS2 repetition is used. Ifrepetition is not used, a value of this field is equal to 0. This valueis constant during the entire duration of the current frame group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates an FEC type used for PLS2that is carried in every frame of a next frame group. The FEC type issignaled according to Table 10.

PLS2_NEXT_MOD: This 3-bit field indicates a modulation type used forPLS2 that is carried in every frame of a next frame group. Themodulation type is signaled according to Table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in a next frame group. When this field is set toa value of ‘1’, the PLS2 repetition mode is activated. When this fieldis set to a value of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicates C_(total) _(_)_(full) _(_) _(block), a size (specified as the number of QAM cells) ofthe collection of full coded blocks for PLS2 that is carried in everyframe of a next frame group, when PLS2 repetition is used. If repetitionis not used in the next frame group, a value of this field is equal to0. This value is constant during the entire duration of a current framegroup.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates a size, inbits, of PLS2-STAT for a next frame group. This value is constant in acurrent frame group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for a next frame group. This value is constant ina current frame group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in a current frame group. This value is constantduring the entire duration of the current frame group. Table 6 belowprovides values of this field. When this field is set to a value of‘00’, additional parity is not used for the PLS2 in the current framegroup.

TABLE 6 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10 to 11Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates a size (specified as thenumber of QAM cells) of additional parity bits of PLS2. This value isconstant during the entire duration of a current frame group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of a next frame group.This value is constant during the entire duration of a current framegroup. Table 12 defines values of this field.

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates a size (specified asthe number of QAM cells) of additional parity bits of PLS2 in everyframe of a next frame group. This value is constant during the entireduration of a current frame group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to all PLS1signaling.

FIG. 25 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 25 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT datais the same within a frame group, while PLS2-DYN data providesinformation that is specific for a current frame.

Details of fields of the PLS2-STAT data are described below.

FIC_FLAG: This 1-bit field indicates whether the FIC is used in acurrent frame group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofa current frame group.

AUX_FLAG: This 1-bit field indicates whether an auxiliary stream is usedin a current frame group. If this field is set to ‘1’, the auxiliarystream is provided in a current frame. If this field set to ‘0’, theauxiliary stream is not carried in the current frame. This value isconstant during the entire duration of current frame group.

NUM_DP: This 6-bit field indicates the number of DPs carried within acurrent frame. A value of this field ranges from 1 to 64, and the numberof DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates a type of a DP. This is signaledaccording to the following Table 7.

TABLE 7 Value DP Type 000 DP Type 1 001 DP Type 2 010 to 111 Reserved

DP_GROUP_ID: This 8-bit field identifies a DP group with which a currentDP is associated. This may be used by the receiver to access DPs ofservice components associated with a particular service having the sameDP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates a DP carrying service signalingdata (such as PSI/SI) used in a management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with service data or a dedicated DP carrying only the servicesignaling data.

DP_FEC_TYPE: This 2-bit field indicates an FEC type used by anassociated DP. The FEC type is signaled according to the following Table8.

TABLE 8 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10 to 11 Reserved

DP_COD: This 4-bit field indicates a code rate used by an associated DP.The code rate is signaled according to the following Table 9.

TABLE 9 Value Code rate 0000 5/15 0001 6/15 0010 7/15 0011 8/15 01009/15 0101 10/15  0110 11/15  0111 12/15  1000 13/15  1001 to 1111Reserved

DP_MOD: This 4-bit field indicates modulation used by an associated DP.The modulation is signaled according to the following Table 10.

TABLE 10 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-1024 1001 to1111 Reserved

DP_SSD_FLAG: This 1-bit field indicates whether an SSD mode is used inan associated DP. If this field is set to a value of ‘1’, SSD is used.If this field is set to a value of ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to an associated DP. A type of MIMO encoding process issignaled according to the following Table 11.

TABLE 11 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010 to 111 Reserved

DP_TI_TYPE: This 1-bit field indicates a type of time interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI block.

DP_TI_LENGTH: The use of this 2-bit field (allowed values are only 1, 2,4, and 8) is determined by values set within the DP_TI_TYPE field asfollows.

If DP_TI_TYPE is set to a value of ‘1’, this field indicates P_(I), thenumber of frames to which each TI group is mapped, and one TI block ispresent per TI group (N_(TI)=1). Allowed values of P_(I) with the 2-bitfield are defined in Table 12 below.

If DP_TI_TYPE is set to a value of ‘0’, this field indicates the numberof TI blocks N_(TI) per TI group, and one TI group is present per frame(P_(I)=1). Allowed values of P_(I) with the 2-bit field are defined inthe following Table 12.

TABLE 12 2-bit field P_(I) N_(TI) 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates a frame interval(I_(JUMP)) within a frame group for an associated DP and allowed valuesare 1, 2, 4, and 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’,or ‘11’, respectively). For DPs that do not appear every frame of theframe group, a value of this field is equal to an interval betweensuccessive frames. For example, if a DP appears on frames 1, 5, 9, 13,etc., this field is set to a value of ‘4’. For DPs that appear in everyframe, this field is set to a value of ‘1’.

DP_TI_BYPASS: This 1-bit field determines availability of the timeinterleaver 5050. If time interleaving is not used for a DP, a value ofthis field is set to ‘1’. If time interleaving is used, the value is setto ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates an index of a first frameof a superframe in which a current DP occurs. A value ofDP_FIRST_FRAME_IDX ranges from 0 to 31.

DP_NUM_BLOCK_MAX: This 10-bit field indicates a maximum value ofDP_NUM_BLOCKS for this DP. A value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates a type of payload datacarried by a given DP. DP_PAYLOAD_TYPE is signaled according to thefollowing Table 13.

TABLE 13 Value Payload type 00 TS 01 IP 10 GS 11 Reserved

DP_INBAND_MODE: This 2-bit field indicates whether a current DP carriesin-band signaling information. An in-band signaling type is signaledaccording to the following Table 14.

TABLE 14 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried 10 INBAND-ISSY is carried 11 INBAND-PLS andINBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates a protocol type of apayload carried by a given DP. The protocol type is signaled accordingto Table 15 below when input payload types are selected.

TABLE 15 If If If DP_PAY- DP_PAY- DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPEValue is TS is IP is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inan input formatting block. A CRC mode is signaled according to thefollowing Table 16.

TABLE 16 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates a null-packet deletion mode used byan associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODE issignaled according to Table 17 below. If DP_PAYLOAD_TYPE is not TS(‘00’), DNP_MODE is set to a value of ‘00’.

TABLE 17 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 Reserved

ISSY_MODE: This 2-bit field indicates an ISSY mode used by an associatedDP when DP_PAYLOAD_TYPE is set to TS (‘00’). ISSY_MODE is signaledaccording to Table 18 below. If DP_PAYLOAD_TYPE is not TS (‘00’),ISSY_MODE is set to the value of ‘00’.

TABLE 18 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 Reserved

HC_MODE_TS: This 2-bit field indicates a TS header compression mode usedby an associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). HC_MODE_TSis signaled according to the following Table 19.

TABLE 19 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates an IP header compression modewhen DP_PAYLOAD_TYPE is set to IP (‘01’). HC_MODE_IP is signaledaccording to the following Table 20.

TABLE 20 Value Header compression mode 00 No compression 01 HC_MODE_IP 110 to 11 Reserved

PID: This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if FIC_FLAG is equal to ‘1’.

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if AUX_FLAG is equal to ‘1’.

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary stream is used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicating atype of a current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 26 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 26 illustrates PLS2-DYN data of the PLS2 data. Values of thePLS2-DYN data may change during the duration of one frame group whilesizes of fields remain constant.

Details of fields of the PLS2-DYN data are as below.

FRAME_INDEX: This 5-bit field indicates a frame index of a current framewithin a superframe. An index of a first frame of the superframe is setto ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration changes. A next superframe with changes in theconfiguration is indicated by a value signaled within this field. Ifthis field is set to a value of ‘0000’, it means that no scheduledchange is foreseen. For example, a value of ‘1’ indicates that there isa change in the next superframe.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration (i.e., content of the FIC) changes. A nextsuperframe with changes in the configuration is indicated by a valuesignaled within this field. If this field is set to a value of ‘0000’,it means that no scheduled change is foreseen. For example, a value of‘0001’ indicates that there is a change in the next superframe.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in a loop over NUM_DP, which describeparameters associated with a DP carried in a current frame.

DP_ID: This 6-bit field uniquely indicates a DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates a start position ofthe first of the DPs using a DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the following Table 21.

TABLE 21 DP_START field size PHY profile 64K 16K Base 13 bits 15 bitsHandheld — 13 bits Advanced 13 bits its

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks in acurrent TI group for a current DP. A value of DP_NUM_BLOCK ranges from 0to 1023.

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate FIC parameters associated with the EAC.

EAC_FLAG: This 1-bit field indicates the presence of the EAC in acurrent frame. This bit is the same value as EAC_FLAG in a preamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates a version number ofa wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated to EAC_LENGTH_BYTE.

If the EAC_FLAG field is equal to ‘0’, the following 12 bits areallocated to EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates a length, in bytes, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of frames before aframe where the EAC arrives.

The following fields appear only if the AUX_FLAG field is equal to ‘1’.

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. A meaning of this field depends on a valueof AUX_STREAM_TYPE in a configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 27 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped to the active carriers of OFDM symbols in a frame. PLS1and PLS2 are first mapped to one or more FSSs. Thereafter, EAC cells, ifany, are mapped to an immediately following PLS field, followed next byFIC cells, if any. The DPs are mapped next after the PLS or after theEAC or the FIC, if any. Type 1 DPs are mapped first and Type 2 DPs aremapped next. Details of types of the DPs will be described later. Insome cases, DPs may carry some special data for EAS or service signalingdata. The auxiliary streams or streams, if any, follow the DPs, which inturn are followed by dummy cells. When the PLS, EAC, FIC, DPs, auxiliarystreams and dummy data cells are mapped all together in the abovementioned order, i.e. the PLS, EAC, FIC, DPs, auxiliary streams anddummy data cells, cell capacity in the frame is exactly filled.

FIG. 28 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) N_(FSS) is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) have higher pilotdensity, allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the FSS(s) in a top-downmanner as shown in the figure. PLS1 cells are mapped first from a firstcell of a first FSS in increasing order of cell index. PLS2 cells followimmediately after a last cell of PLS1 and mapping continues downwarduntil a last cell index of the first FSS. If the total number ofrequired PLS cells exceeds the number of active carriers of one FSS,mapping proceeds to a next FSS and continues in exactly the same manneras the first FSS.

After PLS mapping is completed, DPs are carried next. If an EAC, an FICor both are present in a current frame, the EAC and the FIC are placedbetween the PLS and “normal” DPs.

Hereinafter, description will be given of encoding an FEC structureaccording to an embodiment of the present invention. As above mentioned,the data FEC encoder may perform FEC encoding on an input BBF togenerate an FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The illustrated FEC structure corresponds to theFECBLOCK. In addition, the FECBLOCK and the FEC structure have samevalue corresponding to a length of an LDPC codeword.

As described above, BCH encoding is applied to each BBF (K_(bch) bits),and then LDPC encoding is applied to BCH-encoded BBF (K_(ldpc)bits=N_(bch) bits).

A value of N_(ldpc) is either 64,800 bits (long FECBLOCK) or 16,200 bits(short FECBLOCK).

Table 22 and Table 23 below show FEC encoding parameters for the longFECBLOCK and the short FECBLOCK, respectively.

TABLE 22 LDPC BCH error correction N_(bch) − rate N_(ldpc) K_(ldpc)K_(bch) capability K_(bch) 5/15 64800 21600 21408 12 192 6/15 2592025728 7/15 30240 30048 8/15 34560 34368 9/15 38880 38688 10/15  4320043008 11/15  47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 23 LDPC BCH error correction N_(bch) − rate N_(ldpc) K_(ldpc)K_(bch) capability K_(bch) 5/15 16200 5400 5232 12 168 6/15 6480 63127/15 7560 7392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15 11880 11712 12/15  12960 12792 13/15  14040 13872

Detailed operations of BCH encoding and LDPC encoding are as below.

A 12-error correcting BCH code is used for outer encoding of the BBF. ABCH generator polynomial for the short FECBLOCK and the long FECBLOCKare obtained by multiplying all polynomials together.

LDPC code is used to encode an output of outer BCH encoding. To generatea completed B_(ldpc) (FECBLOCK), P_(ldpc) (parity bits) is encodedsystematically from each I_(ldpc) (BCH—encoded BBF), and appended toI_(ldpc). The completed B_(ldpc) (FECBLOCK) is expressed by thefollowing Equation.

B _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ , i ₁ , . . . , i _(K) _(ldpc) ⁻¹, p ₀ , p ₁ , . . . , p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 2]

Parameters for the long FECBLOCK and the short FECBLOCK are given in theabove Tables 22 and 23, respectively.

A detailed procedure to calculate N_(ldpc)−K_(ldpc) parity bits for thelong FECBLOCK, is as follows.

1) Initialize the parity bits.

p ₀ =p ₁ =p ₂ = . . . =p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹=0   [Equation 3]

2) Accumulate a first information bit-i₀, at a parity bit addressspecified in a first row of addresses of a parity check matrix. Detailsof the addresses of the parity check matrix will be described later. Forexample, for the rate of 13/15,

p₉₈₃=p₉₈₃ ⊕ i₀ p₂₈₁₅=p₂₈₁₅ ⊕ i₀

p₄₈₃₇=p₄₈₃₇ ⊕ i₀ p₄₉₈₉=p₄₉₈₉ ⊕ i₀

p₆₁₃₈=p₆₁₃₈ ⊕ i₀ p₆₄₅₈=p₆₄₅₈ ⊕ i₀

p₆₉₂₁=p₆₉₂₁ ⊕ i₀ p₆₉₇₄=p₆₉₇₄ ⊕ i₀

p₇₅₇₂=p₇₅₇₂ ⊕ i₀ p₈₂₆₀=p₈₂₆₀ ⊕ i₀

p₈₄₉₆=p₈₄₉₆ ⊕ i₀   [Equation 4]

3) For the next 359 information bits, i_(s), s=1, 2, . . . , 359,accumulate i_(s) at parity bit addresses using following Equation.

{x+(s mod 360)×Q_(ldpc)} mod (N_(ldpc)−K_(ldpc))   [Equation 5]

Here, x denotes an address of a parity bit accumulator corresponding toa first bit i₀, and Q_(ldpc) is a code rate dependent constant specifiedin the addresses of the parity check matrix. Continuing with theexample, Q_(ldpc)=24 for the rate of 13/15, so for an information biti₁, the following operations are performed.

p₁₀₀₇=p₁₀₀₇ ⊕ i₁ p₂₈₃₉=p₂₈₃₉ ⊕ i₁

p₄₈₆₁=p₄₈₆₁ ⊕ i₁ p₅₀₁₃=p₅₀₁₃ ⊕ i₁

p₆₁₆₂=p₆₁₆₂ ⊕ i₁ p₆₄₈₂=p₆₄₈₂ ⊕ i₁

p₆₉₄₅=p₆₉₄₅ ⊕ i₁ p₆₉₉₈=p₆₉₉₈ ⊕ i₁

p₇₅₉₆=p₇₅₉₆ ⊕ i₁ p₈₂₈₄=p₈₂₈₄ ⊕ i₁

p₈₅₂₀=p₈₅₂₀ ⊕ i₁   [Equation 6]

4) For a 361th information bit i₃₆₀, an address of the parity bitaccumulator is given in a second row of the addresses of the paritycheck matrix. In a similar manner, addresses of the parity bitaccumulator for the following 359 information bits i_(s), s=361, 362, .. . , 719 are obtained using Equation 6, where x denotes an address ofthe parity bit accumulator corresponding to the information bit i₃₆₀,i.e., an entry in the second row of the addresses of the parity checkmatrix.

5) In a similar manner, for every group of 360 new information bits, anew row from the addresses of the parity check matrix is used to findthe address of the parity bit accumulator.

After all of the information bits are exhausted, a final parity bit isobtained as below.

6) Sequentially perform the following operations starting with i=1.

p _(i) =p _(i) ⊕ p _(i−1) , i=1, 2, . . . , N _(ldpc) −K _(ldpc)−1  [Equation 7]

Here, final content of p_(i) (i=0, 1, . . . , N_(ldpc)−K_(ldpc)−1) isequal to a parity bit p_(i).

TABLE 24 Code rate Q_(ldpc) 5/15 120 6/15 108 7/15 96 8/15 84 9/15 7210/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for the short FECBLOCK is in accordancewith t LDPC encoding procedure for the long FECBLOCK, except that Table24 is replaced with Table 25, and the addresses of the parity checkmatrix for the long FECBLOCK are replaced with the addresses of theparity check matrix for the short FECBLOCK.

TABLE 25 Code rate Q_(ldpc) 5/15 30 6/15 27 7/15 24 8/15 21 9/15 1810/15  15 11/15  12 12/15  9 13/15  6

FIG. 29 illustrates time interleaving according to an embodiment of thepresent invention.

(a) to (c) show examples of a TI mode.

A time interleaver operates at the DP level. Parameters of timeinterleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI.

DP_TI_TYPE (allowed values: 0 or 1): This parameter represents the TImode. The value of ‘0’ indicates a mode with multiple TI blocks (morethan one TI block) per TI group. In this case, one TI group is directlymapped to one frame (no inter-frame interleaving). The value of ‘1’indicates a mode with only one TI block per TI group. In this case, theTI block may be spread over more than one frame (inter-frameinterleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks N_(TI) per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames P_(I) spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): This parameter representsthe maximum number of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, and 8): This parameterrepresents the number of the frames I_(JUMP) between two successiveframes carrying the same DP of a given PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. This parameter is set to ‘0’ iftime interleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the delay compensation block for the dynamic configuration informationfrom the scheduler may still be required. In each DP, the XFECBLOCKsreceived from SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and contains adynamically variable number of XFECBLOCKs. The number of XFECBLOCKs inthe TI group of index n is denoted by N_(xBLOCK) _(_) _(Group)(n) and issignaled as DP_NUM_BLOCK in the PLS2-DYN data. Note that N_(xBLOCK) _(_)_(Group)(n) may vary from a minimum value of 0 to a maximum value ofN_(xBLOCK) _(_) _(Group) _(_) _(MAX) (corresponding toDP_NUM_BLOCK_MAX), the largest value of which is 1023.

Each TI group is either mapped directly to one frame or spread overP_(I) frames. Each TI group is also divided into more than one TI block(N_(TI)), where each TI block corresponds to one usage of a timeinterleaver memory. The TI blocks within the TI group may containslightly different numbers of XFECBLOCKs. If the TI group is dividedinto multiple TI blocks, the TI group is directly mapped to only oneframe. There are three options for time interleaving (except an extraoption of skipping time interleaving) as shown in the following Table26.

TABLE 26 Modes Descriptions Option 1 Each TI group contains one TI blockand is mapped directly to one frame as shown in (a). This option issignaled in PLS2- STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = ‘1’(N_(TI) = 1). Option 2 Each TI group contains one TI block and is mappedto more than one frame, (b) shows an example, where one TI group ismapped to two frames, i.e., DP_TI_LENGTH = ‘2’ (P_(I) = 2) andDP_FRAME_INTERVAL (I_(JUMP) = 2). This provides greater time diversityfor low data-rate services. This option is signaled in PLS2-STAT byDP_TI_TYPE = ‘1’. Option 3 Each TI group is divided into multiple TIblocks and is mapped directly to one frame as shown in (c). Each TIblock may use a full TI memory so as to provide a maximum bit-rate for aDP. This option is signaled in PLS2-STAT by DP_TI_TYPE = ‘0’ andDP_TI_LENGTH = N_(TI), while P_(I) = 1.

Typically, the time interleaver may also function as a buffer for DPdata prior to a process of frame building. This is achieved by means oftwo memory banks for each DP. A first TI block is written to a firstbank. A second TI block is written to a second bank while the first bankis being read from and so on.

The TI is a twisted row-column block interleaver. For an s^(th) TI blockof an n^(th) TI group, the number of rows N_(r) of a TI memory is equalto the number of cells N_(cells), i.e., N_(r)=N_(cells) while the numberof columns N_(c) is equal to the number N_(xBLOCK) _(_) _(TI)(n,s).

FIG. 30 illustrates a basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

FIG. 30(a) shows a write operation in the time interleaver and FIG.30(b) shows a read operation in the time interleaver. A first XFECBLOCKis written column-wise into a first column of a TI memory, and a secondXFECBLOCK is written into a next column, and so on as shown in (a).Then, in an interleaving array, cells are read diagonal-wise. Duringdiagonal-wise reading from a first row (rightwards along a row beginningwith a left-most column) to a last row, N_(r) cells are read out asshown in (b). In detail, assuming z_(n,s,i)(i=0, . . . , N_(r)N_(c)) asa TI memory cell position to be read sequentially, a reading process insuch an interleaving array is performed by calculating a row indexR_(n,s,i), a column index C_(n,s,i), and an associated twistingparameter T_(n,s,i) as in the following Equation.

  [Equation 8] GENERATE (R_(n,s,i), C_(n,s,i)) = { R_(n,s,i) = mod(i,N_(r)), T_(n,s,i) = mod(S_(shift) × R_(n,s,i), N_(c)),$C_{n,s,i} = {{mod}( {{T_{n,s,i} + \lfloor \frac{i}{N_{r}} \rfloor},N_{c}} )}$}

Here, S_(shift) is a common shift value for a diagonal-wise readingprocess regardless of N_(xBLOCK) _(_) _(TI)(n,s), and the shift value isdetermined by N_(xBLOCK) _(_) _(MAX) given in PLS2-STAT as in thefollowing Equation.

$\begin{matrix}{\mspace{20mu} {{for}\{ {\begin{matrix}\begin{matrix}{N_{{xBLOCK}\; \_ \; {TI}\; \_ \; {MA}\; X}^{\prime} =} \\{{N_{{xBLOCK}\; \_ \; {TI}\; \_ \; M\; {AX}} + 1},}\end{matrix} & {{{if}\mspace{14mu} N_{{xBLOCK}\; \_ \; {TI}\; \_ \; {MA}\; X}{mod}\; 2} = 0} \\\begin{matrix}{N_{{xBLOCK}\; \_ \; {TI}\; \_ \; {MA}\; X}^{\prime} =} \\{N_{{xBLOCK}\; \_ \; {TI}\; \_ \; {MA}\; X},}\end{matrix} & {{{if}\mspace{14mu} N_{{xBLOCK}\; \_ \; {TI}\; \_ \; {MA}\; X}{mod}\; 2} = 1}\end{matrix},\mspace{20mu} {S_{shift} = \frac{N_{{xBLOCK}\; \_ \; {TI}\; \_ \; M\; {AX}}^{\prime} - 1}{2}}} }} & \lbrack {{Equation}\mspace{14mu} 9} \rbrack\end{matrix}$

As a result, cell positions to be read are calculated by coordinatesz_(n,s,i)=N_(r)C_(n,s,i)+R_(n,s,i).

FIG. 31 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

More specifically, FIG. 31 illustrates an interleaving array in a TImemory for each TI group, including virtual XFECBLOCKs when N_(xBLOCK)_(_) _(TI)(0,0)=3, N_(xBLOCK) _(_) _(TI)(1,0)=6, and N_(xBLOCK) _(_)_(TI)(2,0)=5.

A variable number N_(xBLOCK) _(_) _(TI)(n,s)=N_(r) may be less than orequal to N′_(xBLOCK) _(_) _(TI) _(_) _(MAX). Thus, in order to achievesingle-memory deinterleaving at a receiver side regardless of N_(xBLOCK)_(_) _(TI)(n,s), the interleaving array for use in the twistedrow-column block interleaver is set to a size ofN_(r)×N_(c)=N_(cells)×N′_(xBLOCK) _(_) _(TI) _(_) _(MAX) by insertingthe virtual XFECBLOCKs into the TI memory and a reading process isaccomplished as in the following Equation.

[Equation 10] p = 0; for i = 0;i < N_(cells)N_(xBLOCK) _(—) _(TI) _(—)_(MAX)′;i = i + 1 {GENERATE (R_(n,s,i), C_(n,s,i)); V_(i) =N_(r)C_(n,s,j) + R_(n,s,j)  if V_(i) < N_(cells)N_(xBLOCK) _(—)_(TI)(n,s)  {   Z_(n,s,p) = V_(i); p = p + 1;   } }

The number of TI groups is set to 3. An option of the time interleaveris signaled in the PLS2-STAT data by DP_TI_TYPE=‘0’,DP_FRAME_INTERVAL=‘1’, and DP_TI_LENGTH=‘1’, i.e., NTI=1, IJUMP=1, andPI=1. The number of XFECBLOCKs, each of which has Ncells=30 cells, perTI group is signaled in the PLS2-DYN data by NxBLOCK_TI(0,0)=3,NxBLOCK_TI(1,0)=6, and NxBLOCK_TI(2,0)=5, respectively. A maximum numberof XFECBLOCKs is signaled in the PLS2-STAT data by NxBLOCK_Group_MAX,which leads to └N_(xBLOCK) _(_) _(Group) _(_) _(MAX)/N_(TI)┘=N_(xBLOCK)_(_) _(TI) _(_) _(MAX)=6.

The purpose of the Frequency Interleaver, which operates on datacorresponding to a single OFDM symbol, is to provide frequency diversityby randomly interleaving data cells received from the frame builder. Inorder to get maximum interleaving gain in a single frame, a differentinterleaving-sequence is used for every OFDM symbol pair comprised oftwo sequential OFDM symbols.

Therefore, the frequency interleaver according to the present embodimentmay include an interleaving address generator for generating aninterleaving address for applying corresponding data to a symbol pair.

FIG. 32 illustrates an interleaving address generator including a mainpseudo-random binary sequence (PRBS) generator and a sub-PRBS generatoraccording to each FFT mode according to an embodiment of the presentinvention.

(a) shows the block diagrams of the interleaving-address generator for8K FFT mode, (b) shows the block diagrams of the interleaving-addressgenerator for 16K FFT mode and (c) shows the block diagrams of theinterleaving-address generator for 32K FFT mode.

The interleaving process for the OFDM symbol pair is described asfollows, exploiting a single interleaving-sequence. First, availabledata cells (the output cells from the Cell Mapper) to be interleaved inone OFDM symbol O_(m,l) is defined as O_(m,l)=[x_(m,l,0), . . . ,x_(m,l,p), . . . , x_(m,l,N) _(data) ⁻¹] for l=0, . . . , N_(sym)−1,where x_(m,l,p) is the p^(th) cell of the l^(th) OFDM symbol in them^(th) frame and N_(data) is the number of data cells: N_(data)=C_(FSS)for the frame signaling symbol(s), N_(data)=C_(data) for the normaldata, and N_(data)=C_(FES) for the frame edge symbol. In addition, theinterleaved data cells are defined as P_(m,l)=[v_(m,l,0), . . . ,v_(m,l,N) _(data) ⁻¹] for l=0, . . . , N_(sym)−1.

-   For the OFDM symbol pair, the interleaved OFDM symbol pair is given    by v_(m,l,H) _(l) _((p))=x_(m,l,p), p=0, . . . , N_(data)−1, for the    first OFDM symbol of each pair v_(m,l,p)=x_(m,l,H) _(l) _((p)), p=0,    . . . , N_(data)−1, for the second OFDM symbol of each pair, where    H_(l)(p) is the interleaving.

address generated by a PRBS generator.

FIG. 33 illustrates a main PRBS used for all FFT modes according to anembodiment of the present invention.

(a) illustrates the main PRBS, and (b) illustrates a parameter Nmax foreach FFT mode.

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleavingaddress for frequency interleaving according to an embodiment of thepresent invention.

(a) illustrates a sub-PRBS generator, and (b) illustrates aninterleaving address for frequency interleaving. A cyclic shift valueaccording to an embodiment of the present invention may be referred toas a symbol offset.

FIG. 35 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

FIG. 35 illustrates a write operation for two TI groups.

A left block in the figure illustrates a TI memory address array, andright blocks in the figure illustrate a write operation when two virtualFEC blocks and one virtual FEC block are inserted into heads of twocontiguous TI groups, respectively.

Hereinafter, description will be given of a configuration of a timeinterleaver and a time interleaving method using both a convolutionalinterleaver (CI) and a block interleaver (BI) or selectively usingeither the CI or the BI according to a physical layer pipe (PLP) mode. APLP according to an embodiment of the present invention is a physicalpath corresponding to the same concept as that of the above-describedDP, and a name of the PLP may be changed by a designer.

A PLP mode according to an embodiment of the present invention mayinclude a single PLP mode or a multi-PLP mode according to the number ofPLPs processed by a broadcast signal transmitter or a broadcast signaltransmission apparatus. The single PLP mode corresponds to a case inwhich one PLP is processed by the broadcast signal transmissionapparatus. The single PLP mode may be referred to as a single PLP.

The multi-PLP mode corresponds to a case in which one or more PLPs areprocessed by the broadcast signal transmission apparatus. The multi-PLPmode may be referred to as multiple PLPs.

In the present invention, time interleaving in which different timeinterleaving schemes are applied according to PLP modes may be referredto as hybrid time interleaving. Hybrid time interleaving according to anembodiment of the present invention is applied for each PLP (or at eachPLP level) in the multi-PLP mode.

FIG. 36 illustrates an interleaving type applied according to the numberof PLPs in a table.

In a time interleaving according to an embodiment of the presentinvention, an interleaving type may be determined based on a value ofPLP_NUM. PLP_NUM is a signaling field indicating a PLP mode. WhenPLP_NUM has a value of 1, the PLP mode corresponds to a single PLP. Thesingle PLP according to the present embodiment may be applied only to aCI.

When PLP_NUM has a value greater than 1, the PLP mode corresponds tomultiple PLPs. The multiple PLPs according to the present embodiment maybe applied to the CI and a BI. In this case, the CI may performinter-frame interleaving, and the BI may perform intra-frameinterleaving.

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver described above.

The hybrid time interleaver according to the first example may include aBI and a CI. The time interleaver of the present invention may bepositioned between a BICM chain block and a frame builder.

The BICM chain block illustrated in FIGS. 37 and 38 may include theblocks in the processing block 5000 of the BICM block illustrated inFIG. 19 except for the time interleaver 5050. The frame builderillustrated in FIGS. 37 and 38 may perform the same function as that ofthe frame building block 1020 of FIG. 18.

As described in the foregoing, it is possible to determine whether toapply the BI according to the first example of the structure of thehybrid time interleaver depending on values of PLP_NUM. That is, whenPLP_NUM=1, the BI is not applied (BI is turned OFF) and only the CI isapplied. When PLP_NUM>1, both the BI and the CI may be applied (BI isturned ON). A structure and an operation of the CI applied whenPLP_NUM>1 may be the same as or similar to a structure and an operationof the CI applied when PLP_NUM=1.

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver described above.

An operation of each block included in the second example of thestructure of the hybrid time interleaver is the same as the abovedescription in FIG. 20. It is possible to determine whether to apply aBI according to the second example of the structure of the hybrid timeinterleaver depending on values of PLP_NUM. Each block of the hybridtime interleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver.

The hybrid time deinterleaver according to the first example may performan operation corresponding to a reverse operation of the hybrid timeinterleaver according to the first example described above. Therefore,the hybrid time deinterleaver according to the first example of FIG. 39may include a convolutional deinterleaver (CDI) and a blockdeinterleaver (BDI).

A structure and an operation of the CDI applied when PLP_NUM>1 may bethe same as or similar to a structure and an operation of the CDIapplied when PLP_NUM=1.

It is possible to determine whether to apply the BDI according to thefirst example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. That is, when PLP_NUM=1, the BDI is notapplied (BDI is turned OFF) and only the CDI is applied.

The CDI of the hybrid time deinterleaver may perform inter-framedeinterleaving, and the BDEI may perform intra-frame deinterleaving.Details of inter-frame deinterleaving and intra-frame deinterleaving arethe same as the above description.

A BICM decoding block illustrated in FIGS. 39 and 40 may perform areverse operation of the BICM chain block of FIGS. 37 and 38.

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver.

The hybrid time deinterleaver according to the second example mayperform an operation corresponding to a reverse operation of the hybridtime interleaver according to the second example described above. Anoperation of each block included in the second example of the structureof the hybrid time deinterleaver may be the same as the abovedescription in FIG. 39.

It is possible to determine whether to apply a BDI according to thesecond example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. Each block of the hybrid timedeinterleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CDI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 41 is a block diagram illustrating a configuration of a broadcastsystem according to an embodiment of the present invention.

The broadcast system according to an embodiment of the present inventionmay provide normal broadcast network services, mobile broadcast networkservices and/or hybrid services.

Normal broadcast network services (ATSC services or DVB services) mayuse full MPD and/or an ATSC SDP. The normal broadcast network servicesdo not use eMBMS MPD, AppSvc MPD and/or 3GPP SDP. The normal broadcastnetwork services (ATSC services or DVB services) may describe and locateall components (ATSC components and/or DVB components) thereof.

Mobile broadcast network services (LTE broadcast services) may use eMBMSMPD (or AppSvc MPD) and/or 3GPP SDP. The mobile broadcast networkservices do not use full MPD and/or ATSC SDP. The mobile broadcastnetwork services may describe and locate all components of 3GPPservices.

Hybrid services (hybrid ATSC/3GPP services) may use full MPD, ATSC SDPand/or 3GPP SDP. The hybrid services may describe and locate allcomponents (ATSC components, DVB components and 3GPP components) ofnormal broadcast network services (ATSC services or DBV services) and/or3GPP services.

The following description is based on the hybrid services.

In addition, the following description is based on audio/video servicesaccording to an embodiment of the present invention. However, an ESGservice may be designated by “ESG” service category. In addition, NTPtime may be indicated in a “well-known” address present in at least onedata pipe (or PLP). An embodiment of the present invention can includeApp enhancement signaling and/or EAS signaling.

A service according to an embodiment of the present invention mayinclude at least one ROUTE session. The service may be transmittedthrough a transport path other than the ROUTE session. If a singleservice includes a single component of a single ROUTE session, theservice can include all components of the ROUTE session.

The broadcast system according to the present embodiment of the presentinvention may include a content provider C410100, a broadcasttransmission apparatus C410200, a second broadcast transmissionapparatus C410300 and/or a broadcast reception apparatus C410500.

The content provider C410100 may provide services (or media content) tothe broadcast transmission apparatus C410200 and/or the second broadcasttransmission apparatus C410300.

The broadcast transmission apparatus C410200 may transmit a broadcastsignal including a service using a normal broadcast network and/or theInternet. The service may include service data and/or signaling data.The broadcast transmission apparatus C410200 may include a firstbroadcast transmission apparatus C410210 using normal broadcast networksand/or a content service C410230 using the Internet. However, the firstbroadcast transmission apparatus C410210 and/or the content serviceC410230 may be included in the single broadcast transmission apparatusC410200 or may be separate apparatuses provided by separate users.

The first broadcast transmission apparatus C410210 may transmit abroadcast signal including a service using a normal broadcast network.The normal broadcast network may be referred to as an ATSC broadcastnetwork and/or a DVB broadcast network. The normal broadcast network mayinclude at least one of a satellite broadcast network, a terrestrialbroadcast network and a cable broadcast network. The first broadcasttransmission apparatus C410210 may include a controller (not shown)and/or a transmitter (not shown). The controller may generate servicedata and signaling data for a service. The transmitter may transmit abroadcast signal including the service data and/or the signaling datausing at least one of normal broadcast networks.

The content server C410230 may transmit a service over the Internet atthe request of the broadcast reception apparatus C410500.

The second broadcast transmission apparatus C410300 may transmit abroadcast signal including a service using a mobile broadcast network.The mobile broadcast network may be referred to as an LTE broadcastnetwork, an LTE network or a mobile network, and the second broadcasttransmission apparatus C410300 may deliver a service to a plurality ofbroadcast reception apparatuses C410500 using the mobile broadcastnetwork. However, the second broadcast transmission apparatus C410300may be provided separately from the broadcast transmission apparatusC410200 or included in the broadcast transmission apparatus C410200.

The broadcast reception apparatus C410500 may include a broadcastreceiver C410510, an IP transceiver C410530 and/or a controller C410550.The broadcast reception apparatus C410500 may control the broadcastreceiver C410510 and/or the IP transceiver C410530 using the controllerC410550. The broadcast reception apparatus C410500 may receive abroadcast signal including a service through a mobile broadcast networkand/or a normal broadcast network using the broadcast receiver C410510.Here, the broadcast signal may be transmitted using at least one of themobile broadcast network and the normal broadcast network. Accordingly,the broadcast reception apparatus C410510 may include a mobile receiverfor receiving broadcast signals, a satellite tuner, a terrestrial tunerand/or a cable tuner. The broadcast reception apparatus C410500 mayrequest the content server C410230 to provide a service through theInternet using the IP transceiver C410530. The broadcast receptionapparatus C410500 may receive a service from the content server over theInternet using the IP transceiver C410530.

FIG. 42 illustrates a configuration of signaling data according to afirst embodiment of the present invention.

The signaling data according to the first embodiment of the presentinvention may include low level signaling data and/or service layersignaling data. The signaling data according to the first embodiment ofthe present invention is applicable even to a mobile environment.

According to the first embodiment of the present invention, SSCbootstrapping information may be transmitted through the low levelsignaling data. Signaling data associated with a service may betransmitted through USD and/or an SMT of the service layer signalingdata.

According to the first embodiment of the present invention, since 3GPPsignaling data is used as signaling data with respect to servicestransmitted over mobile broadcast networks (or LTE broadcast networks)and the Internet, the signaling data with respect to the services canmaintain backward compatibility with mobile environments. In addition,signaling data with respect to services provided through normalbroadcast networks (ATSC broadcast networks or DVB broadcast networks)can include an SMT, a CMT, full MPD and/or an ATSC SDP.

According to the first embodiment of the present invention, thesignaling data includes signaling data with respect to 3GPP and extendssignaling data associated with normal broadcast services (ATSC broadcastservices or DVB broadcast services) which cannot be provided by 3GPP. Inaddition, the signaling data with respect to 3GPP can maintain backwardcompatibility in a mobile environment.

FIG. 42(a) shows low level signaling data according to the firstembodiment of the present invention.

The low level signaling data is signaling information supportingbootstrapping of fast channel scan and service acquisition by areceiver. Bootstrapping of service acquisition may refer to a procedurefor acquiring a service. Accordingly, information for bootstrapping mayinclude path information for service acquisition. For example, the lowlevel signaling data can include a fast information channel (FIC) and/orrating region description (RRD).

The FIC may be referred to as a service list table (SLT). The SLT can beused to form a basic service list and can provide bootstrap discovery ofservice layer signaling data. The SLT can include minimum informationabout a service. For example, the SLT can include service identifierinformation for identifying a service within the range of a specificbroadcast area, service category information for indicating a servicecategory and/or service name information for indicating a service name.For example, a service category can include at least one of a linear A/Vservice, a linear audio only service, an App-based service, anelectronic service guide (ESG) service and an emergency alert service(EAS).

In addition, the SLT may include service layer signaling (SLS)bootstrapping information.

The SLS bootstrapping information may include service signaling channel(SSC) bootstrapping information for at least one service.

For example, an SSC can be a channel through which SLS and/or servicelayer signaling data are transmitted. The SSC bootstrapping informationmay include information for broadcast signaling. SSC bootstrapping mayrefer to a procedure for acquiring an SSC (or service layer signalingdata). Accordingly, the SSC bootstrapping information may include pathinformation for acquiring the service layer signaling data.

The SSC bootstrapping information may include an slsPlpId attributewhich specifies the identifier (PLP ID) of a physical layer pipe throughwhich broadcast SLS (service layer signaling) data for a service istransmitted, an slsDestinationIpAddress attribute which specifies thedotted-IPv4 destination address of packets carrying the broadcast SLSdata for the service, an slsDestinationUdpPort attribute which specifiesthe port number of the packets carrying the broadcast SLS data for theservice and/or an slsSourceIpAddress attribute which specifies thedotted-IPv4 source address of the packets carrying the broadcast SLSdata for the service.

The SLS bootstrapping information may include URL information foraccessing Internet signaling for at least one service.

For example, the URL information can include a URL signaling table (UST)which indicates transport path information (or URL) of at least onesignaling table. The UST may be included not only in service layersignaling data but also in low level signaling data. For example, whenat least one signaling table can be used through broadband, the UST caninclude URLs for MPD, a CMT and/or an application signaling table (AST).The UST may include values referred to as an sltInetUrl element and/oran svcInetUrl element. The sltInetUrl element can indicate a URL foracquiring service level (or layer) signaling files for all services inthe SLT, which can be used through a broadband network (or theInternet). The svcInetUrl element can indicate a URL for acquiringservice level (or layer) signaling files for a specific service, whichcan be used through the broadband network (or the Internet).

The RRD may be referred to as a rating region table (RRT). The RRT mayinclude rating system information about a specific area.

FIG. 42(b) shows service layer signaling data according to the firstembodiment of the present invention.

The service layer signaling data may include information for discoveryand/or acquisition of a service and/or at least one content componentincluded in the service. For example, the service layer signaling datacan include user service description (USD), AppSvc MPD, eMBMS MPD and/or3GPP SDP. In addition, the service layer signaling data may include aservice map table (SMT), a component map table (CMT), a URL signalingtable (UST), rating region description (RRD), full MPD, an ATSC SDPand/or LSID. The USD, AppSvc MPD, eMBMS MPD and/or 3GPP SDP may besignaling data for mobile broadcast networks. The SMT, CMT, UST, RRD,full MPD, ATSC SDP and/or LSID may be signaling data for normalbroadcast networks. For example, the SMT can be referred to as userservice bundle description/user service description (USBD/USD). TheUSBD/USD is a kind of a service layer signaling (SLS) XML fragmentserving as a signaling hub which describes details of technicalinformation for services. In addition, the CMT, UST, RRD, ATSC SDPand/or LSID may be referred to as service-based transport sessioninstance description (S-TSID). The S-TSID is a kind of an SLS XMLfragment which provides session description information for at least onetransport session through which at least one content component of aservice is transmitted.

The USD may be multimedia broadcast/multicast service (MBMS) userservice description of 3rd generation partnership project (3GPP). TheUSD may include transport path information for AppSvc MPD, eMBMS MPDand/or 3GPP SDP.

The AppSvc MPD may be dynamic adaptive streaming over HTTP (DASH) MPDfor at least one 3GPP broadcast & unicast component.

The eMBMS MPD may be DASH MPD for at least one component transmittedthrough an evolved multimedia broadcast multicast system (eMBMS) bearer.

The 3GPP SDP may be an IETF session description protocol (SDP) for atleast one eMBMS FLUTE session.

The SMT may include path information for acquiring attribute (ID, name,category, etc.) information of a service and the service. For example,the SMT can include transport path information for the full MPD and/orthe ATSC SDP. The SMT may be ATSC extensions. In addition, the SMT maybe replaced by SPD and/or service configuration description (SCD). TheSCD may include a large amount of additional signaling information whichis not included in the FIC. The SMT may be referred to as USBD/USD. TheUSBD/USD is a kind of an SLS XML fragment serving as a signaling hubwhich describes details of technical information for services.

The CMT may include information related to a component, such ascomponent information (associated DASH representation information) for aservice and a path through which the component can be acquired. Forexample, the CMT can include the identifier (DP ID or PLP ID) of aphysical layer pipe through which component data for a service istransmitted.

The UST may include transport path information (or URL) of at least onesignaling table. For example, when the at least one signaling table canbe used through a broadband network, the UST can include URLs for MPD,CMT and/or application signaling table (AST).

The RRD may include rating system information about a specific area.

The full MPD may include DASH MPD with respect to all components of aservice. For example, the full MPD can include DASH MPD with respect toall components transmitted through mobile broadcast networks, normalbroadcast networks and/or the Internet. The DASH MPD may includeformalized description of DASH media presentation. The DASH MPD mayinclude resource identifiers for individual media components oflinear/streaming services. In addition, the DASH MPD may include contextof resources specified in media presentation. For example, a resourceidentifier can be information for identifying representation associatedwith a component for a service. For example, the resource identifier canhave the form of a segment URL.

The ATSC SDP may include at least one ROUTE session element whichprovides information about at least one real-time object delivery overunidirectional transport (ROUTE) for a service and/or componentsincluded in the service. The ATSC SDP may be an IETF SDP for at leastone ROUTE session. A ROUTE session element may include transport pathinformation for a ROUTE session. For example, the ROUTE session elementcan include a bsid attribute which specifies the identifier of abroadcast stream through which a content component of a service istransmitted, an sIpAddr attribute which specifies the source IP addressof the ROUTE session, a dIpAddr attribute which specifies thedestination IP address of the ROUTE session, a dport attribute whichspecifies the destination port number of the ROUTE session and/or aPLPID attribute which specifies a physical layer parameter for the ROUTEsession. The bsid attribute, sIPAddr attribute, dIpAddr attribute, dportattribute and/or PLPID attribute may be used as information on a paththrough which LSID is transmitted. The ATSC SDP may be included inS-TSID. The S-TSID is a kind of SLS XML fragment which provides sessiondescription information for at least one transport session through whichat least one content component of a service is transmitted.

LCT session ID description (LSID) may include information for specifyinga transport session through which a component of a service istransmitted. The LSID may be included in each ROUTE session. The LSIDmay be transmitted through a specific transport session in a ROUTEsession. In addition, the LSID may include information about a layeredcoding transport (LCT) session included in a ROUTE session. For example,the LSID can include a tsi attribute which specifies a transport sessionthrough which a content component for a service is transmitted and/or aPLPID attribute which specifies the identifier of a physical layer pipeassociated with the transport session through which the contentcomponent for the service is transmitted.

A broadcast reception apparatus according to an embodiment of thepresent invention can acquire a service on the basis of signaling data.Specifically, the broadcast reception apparatus can acquire low levelsignaling data and obtain service layer signaling data on the basis ofthe low level signaling data. Then, the broadcast reception apparatuscan determine properties of a service using service layer signaling data(USD and/or SMT). Subsequently, the broadcast reception apparatus canselect at least one component for the service using service layersignaling data (MPD). For example, the broadcast reception apparatus canselect at least one component for the service using at least onerepresentation ID of the MPD. Then, the broadcast reception apparatuscan acquire information on a transport path through which the selectedat least one component is transmitted using service layer signaling data(SDP, LSID and/or CMT).

FIG. 43 illustrates a service according to the first embodiment of thepresent invention.

FIG. 43(a) shows signaling data according to the first embodiment of thepresent invention. The signaling data may be transmitted by the firstbroadcast transmission apparatus. However, the present invention is notlimited thereto and the signaling data may be transmitted by the secondbroadcast transmission apparatus and/or the content server.

The signaling data may include low level signaling data and/or servicelayer signaling data.

The low level signaling data may include information for bootstrapdiscovery of the service layer signaling data.

The service layer signaling data may include USD, AppSvc MPD, eMBMS MPDand/or 3GPP SDP. The USD, AppSvc MPD, eMBMS MPD and/or 3GPP SDP may besignaling data for mobile broadcast networks only.

The USD may include transport path information for the AppSvc MPD, eMBMSMPD and/or 3GPP SDP. In addition, the USD may include a deliveryMethodelement which indicates a container of transport related informationassociated with service content transmitted through a broadcast accessmode and/or a broadband access mode. The deliveryMethod element mayinclude a broadcastAppService element and/or a unicastAppServiceelement.

The broadcastAppService element may indicate DASH representationincluding media components corresponding to a service, which aretransmitted through a mobile broadcast network, over all periods ofaffiliated media presentation. A basePattern element included in thebroadcastAppService element may refer to segment URL information mappedto each component in MPD. For example, the broadcastAppService elementcan indicate “UHD video component” and the basePattern element canindicate “basePattern1”.

The unicastAppService element may indicate DASH representation includingconfiguration media content components belonging to the service, whichare transmitted through a broadband network (Internet) over all periodsof affiliated media presentation. The basePattern element included inthe broadcastAppService element may refer to segment URL informationmapped to each component in MPD. For example, the unicastAppServiceelement can indicate a second audio component and the basePatternelement can indicate “basePattern4”.

The AppSvc MPD may include information about the second audio componenthaving segment URL information of “basePattern4”.

The eMBMS MPD may include information about a UHD video component havingsegment URL information of “basePattern1”.

The service layer signaling data may include an SMT, a CMT, full MPD, anATSC SDP and/or LSID. The SMT, CMT, full MPD, ATSC SDP and/or LSID maybe signaling data for normal broadcast networks.

The SMT may include transport path information for the full MPD and/orthe ATSC SDP. The SMT may include information about an HD videocomponent and information about a first audio component.

The ATSC SDP may include information about at least one ROUTE sessionfor a service and/or components included in the service.

The full MPD may include information about the UHD video componenthaving segment URL information of “basePattern1”. In addition, the fullMPD may include information about the HD video component havingrepresentation ID information of “rep_id2”. Furthermore, the full MPDmay include information about the first audio component havingrepresentation ID information of “rep_id3”. The full MPD may includeinformation about the second audio component having segment URLinformation of “basePattern4”.

The CMT may include a BroadcastComp element including mappinginformation of components transmitted through a normal broadcast networkand/or a broadbandComp element including mapping information ofcomponents transmitted over the Internet. For example, the BroadcastCompelement can include a first BroadcastComp element including mappinginformation of the HD video component transmitted through the normalbroadcast network and/or a second BroadcastComp element includingmapping information of the first audio component transmitted through thenormal broadcast network. Each of the first BroadcastComp element andthe second BroadcastComp element may include a Rep_ID attribute whichindicates a DASH representation identifier associated with thecorresponding component and/or a DP_ID attribute which indicates theidentifier of a data pipe (DP) (or PLP) through which the correspondingcomponent data is transmitted in a broadcast stream. The Rep_IDattribute of the first BroadcastComp can indicate “rep_id2” and theDP_ID attribute of the first BroadcastComp can indicate can indicate“DP_id2”. The Rep_ID attribute of the second BroadcastComp can indicate“rep_id3” and the DP_ID attribute of the second BroadcastComp canindicate “DP_id3”.

The BroadbandComp element may include a reptnID attribute whichindicates a DASH representation identifier associated with thecorresponding component and/or a baseURL attribute which indicates abase URL of segments constituting DASH representation associated withthe corresponding component. The baseURL attribute of the BroadbandCompelement may indicate “basePattern4”. That is, transport path informationof the second audio component transmitted over the Internet can be“basePattern4”.

The LSID can be acquired on the basis of information about ROUTEsessions.

Details of the signaling data correspond to the contents of theaforementioned signaling data.

Referring to FIG. 43(b), a broadcast transmission apparatus(broadcaster) C430200 according to the first embodiment of the presentinvention can transmit service data and/or signaling data for a serviceusing a normal broadcast network and/or the Internet. For example, thebroadcaster C430200 can transmit service data and/or signaling data fora service through a normal broadcast network using a first broadcasttransmission apparatus (not shown). The broadcaster C430200 can transmitservice data and/or signaling data for a service over the Internet usinga content server (not shown). A second broadcast transmission apparatus(mobile carrier) C430300 can transmit service data and/or signaling datafor a service using a mobile broadcast network (e.g. LTE broadcast).

The first broadcast transmission apparatus may transmit a videocomponent and a first audio component of a base layer for a serviceusing a normal broadcast network. For example, the video component ofthe base layer can be an HD video component. The HD video component canbe matched to “Rep_id2” of MPD and the first audio component can bematched to “Rep_id3” of MPD. In addition, the HD video component and/orthe first audio component can be transmitted through a predetermineddata pipe (DP) and/or a physical layer pipe (PLP). For example, thepredetermined DP has an identifier of “DP_id3”.

The content server may transmit a second audio component for the serviceusing the Internet. For example, information on the path through whichthe second audio component is transmitted can be “basePattern4”.

The second broadcast transmission apparatus C430300 may transmit a videocomponent of an enhanced layer for the service using a mobile broadcastnetwork (LTE broadcast). For example, the video component of theenhanced layer can be a UHD video component. The video component of theenhanced layer may be additional information for generating UHD video.In addition, information on the path through which the UHD videocomponent is transmitted can be “basePattern1”.

A broadcast reception apparatus C430500 according to the firstembodiment of the present invention may receive service data and/orsignaling data for services. The broadcast reception apparatus C430500can receive the HD video component and/or the first audio component fromthe broadcast transmission apparatus C430200 using a broadcast receiver.The broadcast reception apparatus C430500 can receive the second audiocomponent from the broadcast transmission apparatus C430200 using an IPtransceiver. The broadcast reception apparatus C430500 can receive theUHD video component from the second broadcast transmission apparatusC430300 using the broadcast receiver. The broadcast reception apparatusC430500 can acquire the HD video component, the first audio component,the second audio component and/or the UHD video component on the basisof the capability and environment thereof and decode and/or reproducethe acquired data.

FIG. 44 shows an SMT according to the first embodiment of the presentinvention.

The signaling data according to the first embodiment of the presentinvention may include low level signaling data and/or service layersignaling data. The service layer signaling data may include a servicemap table (SMT).

The SMT may include properties of a service and information on a paththrough which the service can be acquired. The SMT may be referred to asUSBD/USD. The USBD/USD is a kind of a service layer signaling (SLS) XMLfragment serving as a signaling hub which describes details of technicalinformation for services.

The SMT may include a protocol_version attribute, a service_idattribute, a global_service_id attribute, a Full_MPD_URL attribute, anATSC_SDP_URL attribute, a Capabilities attribute, a Targeting_infoattribute, a Content_advisory attribute, a Program_title attribute, aContent_label attribute and/or an Original service id attribute.

The protocol_version attribute may indicate the protocol version of anSSC (service signaling channel or service layer signaling data). Forexample, the protocol_version attribute can include amajor_protocol_version attribute which indicates the major versionnumber of a protocol used to transmit an SSC (service signaling channel,S-TSID and/or service layer signaling data) for a service and/or aminor_protocol_version attribute which indicates the minor versionnumber of the protocol.

The service_id attribute is a unique identifier for identifying aservice. The service_id attribute may refer to a service entrycorresponding to low level signaling data (LLS, FIC or SLT). Theservice_id attribute may have the same value as a service identifier(serviceID) allocated to the service entry corresponding to the lowlevel signaling data (LLS, FIC or SLT).

The global_service_id attribute is a globally unique identifier used forservice mapping between 3GPP USD and an ESG. The global_service_idattribute may have the same value as the service identifier (service_id)of the 3GPP USD and the service identifier (service_id) of the ESG. Theglobal_service_id attribute is a globally unique uniform resourceidentifier (URI) for identifying a service. The global_service_idattribute is a unique value within the range of broadcast streamidentifiers (BSID). In addition, the global_service_id attribute may beused to access ESG data.

The Full_MPD_URL attribute indicates information (URL information or URIinformation) referring to MPD including information about all contentcomponents of a service transmitted through at least one of a mobilebroadcast network (LTE broadcast), the Internet (unicast) and a normalbroadcast network (ATSC broadcast or DVB broadcast).

The ATSC_SDP_URL attribute refers to information (URL information norURI information) indicating an SDP including information about a ROUTEsession through which a service (ATSC service or a DVB service) istransmitted. The ATSC_SDP_URL attribute is information (URL informationor URI information) which refers to S-TSID (or ATSC_SDP) which providesaccess related parameters with respect to transport sessions throughwhich service content is delivered.

The Capabilities attribute refers to a descriptor which describescapability that a receiver needs to have in order to provide services.The Capabilities attribute may specify capabilities and/or capabilitygroups necessary for the receiver to achieve meaningful reproduction ofcontent of services.

The Targeting_info attribute may indicate a target device to which aservice will be provided.

The Content_advisory attribute may refer to information about contentadvisory related to a provided service. The Content_advisory attributemay specify content advisory rating with respect to the providedservice.

The Program_title attribute may refer to information about the title ofa service. The Program_title attribute may indicate the name of aservice in a specific language.

The Content_label attribute may refer to a content label of a service.The Content_label attribute may indicate the name of a component.

The Original service id attribute may refer to an ID assigned to theoriginal service of a corresponding service.

FIG. 45 illustrates a configuration of signaling data according to asecond embodiment of the present invention.

The signaling data according to the second embodiment may include lowlevel signaling data and/or service layer signaling data. The signalingdata according to the second embodiment of the present invention isapplicable even to a mobile environment.

According to the second embodiment of the present invention, SSCbootstrapping information may be transmitted through the low levelsignaling data. Signaling data associated with a service and/orsignaling data associated with a component can be transmitted throughUSD of the service layer signaling data.

The second embodiment of the present invention can provide a servicesignaling method for services transmitted through mobile broadcastnetworks (LTE broadcast), the Internet (unicast) and/or normal broadcastnetworks (ATSC broadcast or DVB broadcast) by extending 3GPP USD.

The second embodiment of the present invention provides a servicesignaling method without using a CMT which provides component locationinformation from among ATSC signaling tables, by adding the ID (DP_ID orPLP_ID) of a data pipe (physical layer pipe) through which a componentis delivered to an atscAppService element included in aUSBD/USD/Delivery method.

The SSC bootstrapping information is transmitted through an FIC, and anSSC delivered through the SSC bootstrapping information includes USD.

A description will be given of USD extension according to the secondembodiment of the present invention.

FIG. 45(a) illustrates the low level signaling data according to thesecond embodiment of the present invention.

The low level signaling data is signaling information supportingbootstrapping of fast channel scan and service acquisition by areceiver. For example, the low level signaling data can include a fastinformation channel (FIC) and/or rating region description (RRD).

The contents of the low level signaling data according to the secondembodiment of the present invention can include the contents of theaforementioned low level signaling data.

FIG. 45(b) illustrates the service layer signaling data according to thesecond embodiment of the present invention.

The contents of the low level signaling data according to the secondembodiment of the present invention can include the contents of theaforementioned low level signaling data. The following description isbased on a difference between the low level signaling data according tothe second embodiment of the present invention and the aforementionedlow level signaling data.

The service layer signaling data may include user service description(USD), AppSvc MPD, eMBMS MPD and/or 3GPP SDP. In addition, the servicelayer signaling data may include full MPD, ATSC SDP and/or LSID. TheAppSvc MPD, eMBMS MPD and/or 3GPP SDP may be signaling data for mobilebroadcast networks. The USD, full MPD, ATSC SDP and/or LSID may besignaling data for normal broadcast networks.

The USBD/USD is a kind of a service layer signaling (SLS) XML fragmentserving as a signaling hub which describes details of technicalinformation for services.

The USD may include transport path information for the AppSvc MPD, eMBMSMPD and/or 3GPP SDP.

In addition, the USD may include a deliveryMethod element and/or anatscServiceDescription element.

The deliveryMethod element may include a broadcastAppService element formobile broadcast networks, a unicastAppService element for the Internetand/or an atscAppService element for normal broadcast networks.

Each of the broadcastAppService element, unicastAppService elementand/or atscAppService element may include a basePattern element. ThebasePattern element may refer to information about a segment URL towhich each component is mapped in MPD.

The atscServiceDescription element may refer to DASH representationincluding configuration media content components belonging to a service,which are transmitted through a normal broadcast network (ATSC broadcastor DVB broadcast) over all periods of affiliated media presentation.

The atscServiceDescription element may include the ID (DP_ID or PLP_ID)of a physical layer pipe through which component data for a service isdelivered.

The atscServiceDescription element may include information about aservice transmitted through a normal broadcast network.

The atscServiceDescription element may include information aboutproperties (ID, name, category and the like) of a service andinformation about a path through which the service can be acquired. Forexample, the atscServiceDescription element can include path informationfor the full MPD and/or ATSC SDP.

The full MPD may include DASH MPD with respect to all components of aservice.

The ATSC SDP may include at least one ROUTE session element whichprovides information about at least one real-time object delivery overunidirectional transport (ROUTE) for a service and/or a componentincluded in the service.

LCT session ID description (LSID) may include information for specifyinga transport session through which a component for a service istransmitted. The LSID may include information about an LCT sessionincluded in a ROUTE session.

A broadcast reception apparatus according to the present embodiment mayacquire a service on the basis of signaling data. Specifically, thebroadcast reception apparatus may acquire low level signaling data andacquire service layer signaling data on the basis of the low levelsignaling data. Then, the broadcast reception apparatus may determineproperties of a service using service layer signaling data (USD).Subsequently, the broadcast reception apparatus may select at least onecomponent for the service using service layer signaling data (MPD). Forexample, the broadcast reception apparatus can select at least onecomponent for the service using at least one representation ID of theMPD. Then, the broadcast reception apparatus may acquire information ona transport path through which the selected at least one component istransmitted using service layer signaling data (SDP and/or LSID).

FIG. 46 illustrates the USD according to the second embodiment of thepresent invention.

The extended USD according to the second embodiment of the presentinvention may include the atscServiceDescription element C460100 and/oratscAppService element C460200.

The atscServiceDescription element C460100 may include attributes of aservice and/or information about a path through which the service can beacquired. The atscServiceDescription element C460100 may include aProtocolVersion attribute, an atscServiceId attribute, a GlobalServiceIdattribute, a FullmpdURL attribute, an atscSdpURL element, aCapabilityDescription element, a TargetingDescription element, aContentAdvisoryDescription element, a ProgramTitleDescription element, aContentLabelDescription element and/or an OriginalServiceId element.

The ProtocolVersion attribute corresponds to the aforementionedprotocol_version attribute, the atscServiceId attribute corresponds tothe aforementioned service_id attribute, the GlobalServiceId attributecorresponds to the aforementioned global_service_id attribute, theFullmpdURL attribute corresponds to the aforementioned Full_MPDattribute, the atscSdpURL element corresponds to the aforementionedATSC_SDP_URL attribute, the CapabilityDescription element corresponds tothe aforementioned Capabilities attribute, the TargetingDescriptionelement corresponds to the aforementioned Targeting_info attribute, theContentAdvisoryDescription element corresponds to the aforementionedcontent_advisory attribute, the ProgramTitleDescription elementcorresponds to the aforementioned Program_title attribute, theContentLabelDescription element corresponds to the aforementionedContent_label attribute and the OriginalServiceId element corresponds tothe aforementioned Original service id attribute.

Although “element” and “attribute” are used in the embodiments,functions thereof may be identical.

The atscServiceDescription element C460100 may be commonly used in thesecond, third and fourth embodiments of the present invention.

The atscAppService element C460200 may indicate DASH representationincluding configuration media content components belonging to a service,which are transmitted through a normal broadcast network (ATSC broadcastor DVB broadcast) over all periods of affiliated media presentation. TheatscAppService element C460200 may include a basePattern attribute, aDP_ID attribute, a transportStreamID attribute, a partitionId attribute,a sourceIPaddress attribute, a destinationIPaddress attribute and/or adestinationPort attribute.

The basePattern attribute refers to segment URL information to whicheach component is mapped in MPD.

The DP_ID attribute refers to the ID of a data pipe (or physical layerpipe) through which a component is transmitted. The DP_ID attribute isthe ID (DP_ID or PLP_ID) of a physical layer pipe through whichcomponent data for a service is transmitted.

The transportStreamID attribute indicates the ID of a broadcast streamincluding the corresponding component data.

The partitionId attribute indicates the ID of a partition indicating abroadcasting station in the corresponding broadcast stream.

The sourceIPaddress attribute indicates the source IP address of an IPdatagram including the corresponding component data.

The destinationIPaddress attribute indicates the destination IP addressof the IP datagram including the corresponding component data.

The destinationPort attribute indicates the destination UDP port numberof the IP datagram including the corresponding component data.

The transportStreamID attribute, the partitionId attribute, thesourceIPaddress attribute and/or the destinationIPaddress attribute mayprovide component information transmitted through foreign ATSCbroadcast.

Since the atscAppService element C460200 included in the USD containsthe DP_ID attribute, the service layer signaling data according to thesecond embodiment of the present invention may not include the CMT.

FIG. 47 illustrates a service according to the second embodiment of thepresent invention.

FIG. 47(a) shows signaling data according to the second embodiment ofthe present invention. The signaling data may be transmitted by thefirst broadcast transmission apparatus. However, the present inventionis not limited thereto and the signaling data may be transmitted by thesecond broadcast transmission apparatus and/or the content server.

The signaling data may include low level signaling data and/or servicelayer signaling data. The contents of the signaling data according tothe second embodiment of the present invention may include the contentsof the aforementioned signaling data. The following description is basedon a difference between the signaling data according to the secondembodiment of the present invention and the aforementioned signalingdata.

The service layer signaling data may include USD, full MPD, ATSC SDPand/or LSID.

The USD may include transport path information for the full MPD and/orATSC SDP.

The USD may include the broadcastAppService element for mobile broadcastnetworks, the unicastAppService element for the Internet and/or theatscAppService element C460200 for normal broadcast networks.

The broadcastAppService element may specify “UHD video component” andthe basePattern element may specify “basePattern1”.

The unicastAppService element may specify a second audio component andthe basePattern element may specify “basePattern4”.

The atscAppService element may include a first atscAppService elementfor an HD video component and a second atscAppService element for afirst audio component. The first atscAppService element may indicate “HDvideo component”, the basePattern attribute may indicate “basePattern2”and the DP_ID attribute may specify “DP_id3”. The second atscAppServiceelement may indicate “first audio component”, the basePattern attributemay indicate “basePattern3” and the DP_ID attribute may specify“DP_id3”.

The ATSC SDP may include information about at least one ROUTE sessionfor a service and/or a component included in the service.

The full MPD may include information about the UHD video componenthaving segment URL information of “basePattern1”. In addition, the fullMPD may include information about the HD video component having segmentURL information (or representation ID information) of “basePattern2”.Furthermore, the full MPD may include information about the first audiocomponent having segment URL information (or representation IDinformation) of “basePattern3”. The full MPD may include informationabout the second audio component having segment URL information of“basePattern4”.

The LSID can be acquired on the basis of information about ROUTEsessions.

Referring to FIG. 47(b), a broadcast transmission apparatus(broadcaster) C470200 according to the second embodiment of the presentinvention may transmit service data and/or signaling data for servicesusing normal broadcast networks and/or the Internet. For example, thebroadcaster C470200 can transmit service data and/or signaling data forservices through a normal broadcast network using a first broadcasttransmission apparatus (not shown). The broadcaster C470200 can transmitservice data and/or signaling data for services over the Internet usinga content server (not shown). A second broadcast transmission apparatus(mobile carrier) C470300 can transmit service data and/or signaling datafor services using a mobile broadcast network (e.g. LTE broadcast).

The first broadcast transmission apparatus may transmit a videocomponent and a first audio component of a base layer for a serviceusing a normal broadcast network. For example, the video component ofthe base layer can be an HD video component. Information about a paththrough which the HD video component is transmitted can be“basePattern2” and information about a path through which the firstaudio component is transmitted can be “basePattern3”. In addition, theHD video component and/or the first audio component can be transmittedthrough a predetermined data pipe (DP) and/or a physical layer pipe(PLP). For example, the predetermined DP can have an identifier of“DP_id3”.

The content server may transmit a second audio component for the serviceusing the Internet. For example, information on the path through whichthe second audio component is transmitted can be “basePattern4”.

The second broadcast transmission apparatus C470300 may transmit a videocomponent of an enhanced layer for the service using a mobile broadcastnetwork (LTE broadcast). For example, the video component of theenhanced layer can be a UHD video component. The video component of theenhanced layer may be additional information for generating UHD video.In addition, information on the path through which the UHD videocomponent is transmitted can be “basePattern1”.

A broadcast reception apparatus C470500 according to the secondembodiment of the present invention may receive service data and/orsignaling data for services. The broadcast reception apparatus C470500may receive the HD video component and/or the first audio component fromthe broadcast transmission apparatus C470200 using a broadcast receiver.The broadcast reception apparatus C470500 may receive the second audiocomponent from the broadcast transmission apparatus C470200 using an IPtransceiver. The broadcast reception apparatus C470500 may receive theUHD video component from the second broadcast transmission apparatusC470300 using the broadcast receiver. The broadcast reception apparatusC470500 may acquire the HD video component, the first audio component,the second audio component and/or the UHD video component on the basisof the capabilities and environment thereof and decode and/or reproducethe acquired data.

FIG. 48 illustrates a configuration of signaling data according to athird embodiment of the present invention.

The signaling data according to the third embodiment may include lowlevel signaling data and/or service layer signaling data. The signalingdata according to the third embodiment of the present invention isapplicable even to a mobile environment.

According to the third embodiment of the present invention, SSCbootstrapping information may be transmitted through the low levelsignaling data. Signaling data associated with a service may betransmitted through USD of the service layer signaling data andsignaling data associated with a component may be transmitted through aCMT of the service layer signaling data.

The third embodiment of the present invention can provide a servicesignaling method for services transmitted through mobile broadcastnetworks (LTE broadcast), the Internet (unicast) and/or normal broadcastnetworks (ATSC broadcast or DVB broadcast) by extending 3GPP USD.

The SSC bootstrapping information is transmitted through an FIC and anSSC delivered through the SSC bootstrapping information includes USD.

A description will be given of USD extension according to the thirdembodiment of the present invention.

FIG. 48(a) illustrates the low level signaling data according to thethird embodiment of the present invention.

The low level signaling data is signaling information supportingbootstrapping of fast channel scan and service acquisition by areceiver. For example, the low level signaling data can include a fastinformation channel (FIC) and/or rating region description (RRD).

The contents of the low level signaling data according to the thirdembodiment of the present invention can include the contents of theaforementioned low level signaling data.

FIG. 48(b) illustrates the service layer signaling data according to thethird embodiment of the present invention.

The contents of the low level signaling data according to the thirdembodiment of the present invention can include the contents of theaforementioned low level signaling data. The following description isbased on a difference between the low level signaling data according tothe third embodiment of the present invention and the aforementioned lowlevel signaling data.

The service layer signaling data may include USD, AppSvc MPD, eMBMS MPDand/or 3GPP SDP. In addition, the service layer signaling data mayinclude full MPD, ATSC SDP, CMT and/or LSID. The AppSvc MPD, eMBMS MPDand/or 3GPP SDP may be signaling data for mobile broadcast networks. TheUSD, full MPD, ATSC SDP, CMT and/or LSID may be signaling data fornormal broadcast networks.

The USD may include a deliveryMethod element and/or anatscServiceDescription element.

The deliveryMethod element may include a broadcastAppService element formobile broadcast networks, a unicastAppService element for the Internetand/or an atscAppService element for normal broadcast networks.

Each of the broadcastAppService element, unicastAppService elementand/or atscAppService element may include a basePattern element. ThebasePattern element may refer to information about a segment URL towhich each component is mapped in MPD.

The CMT may include component related information such as componentinformation (associated DASH representation information) for a serviceand a path through which the corresponding component can be acquired.

For example, the CMT can include a basePattern element which refers tosegment URL information to which each component is mapped in MPD.

In addition, the CMT may include the ID (DP ID or PLP ID) of a physicallayer pipe (data pipe) through which component data for the service istransmitted.

A broadcast reception apparatus according to the third embodiment of thepresent invention can acquire a service on the basis of signaling data.Specifically, the broadcast reception apparatus can acquire low levelsignaling data and acquire service layer signaling data on the basis ofthe low level signaling data. Then, the broadcast reception apparatuscan determine properties of a service using service layer signaling data(USD). Subsequently, the broadcast reception apparatus can select atleast one component for the service using service layer signaling data(MPD). For example, the broadcast reception apparatus can select atleast one component for the service using at least one representation IDof the MPD. Then, the broadcast reception apparatus can acquireinformation on a transport path through which the selected at least onecomponent is transmitted using the service layer signaling data (SDP,CMT and/or LSID).

FIG. 49 illustrates the USD according to the third embodiment of thepresent invention.

The extended USD according to the third embodiment of the presentinvention may include the atscServiceDescription element C490100 and/oratscAppService element C490200.

The atscServiceDescription element C490100 may include attributes of aservice and/or information about a path through which the service can beacquired. The atscServiceDescription element C490100 may include aProtocolVersion attribute, an atscServiceId attribute, a GlobalServiceIdattribute, a FullMpdURL attribute, an atscSdpURL element, aCapabilityDescription element, a TargetingDescription element, aContentAdvisoryDescription element, a ProgramTitleDescription element, aContentLabelDescription element and/or an OriginalServiceId element.

The contents of the atscServiceDescription element C490100 according tothe third embodiment of the present invention can include the contentsof the aforementioned atscServiceDescription element.

The atscAppService element C490200 may indicate DASH representationincluding configuration media content components belonging to a service,which are transmitted through a normal broadcast network (ATSC broadcastor DVB broadcast) over all periods of affiliated media presentation. TheatscAppService element C490200 may include a basePattern attribute, atransportStreamID attribute, a partitionId attribute, a sourceIPaddressattribute, a destinationIPaddress attribute and/or a destinationPortattribute.

The contents of the atscAppService element C490200 according to thethird embodiment of the present invention can include the contents ofthe aforementioned atscAppService element.

The atscAppService element C490200 may further include a Rep_idattribute. The Rep_id attribute refers to representation ID informationto which each component is mapped in MPD.

According to the third embodiment of the present invention, the ID(DP_ID attribute or PLP_ID attribute) of a physical layer pipe (datapipe) through which component data for a service is transmitted may beincluded in the CMT instead of the atscAppService element C490200.

FIG. 50 illustrates a service according to the third embodiment of thepresent invention.

FIG. 50(a) shows signaling data according to the third embodiment of thepresent invention. The signaling data may be transmitted by the firstbroadcast transmission apparatus. However, the present invention is notlimited thereto and the signaling data may be transmitted by the secondbroadcast transmission apparatus and/or the content server.

The signaling data may include low level signaling data and/or servicelayer signaling data. The contents of the signaling data according tothe third embodiment of the present invention may include the contentsof the aforementioned signaling data. The following description is basedon a difference between the signaling data according to the secondembodiment of the present invention and the aforementioned signalingdata.

The service layer signaling data may include USD, full MPD, ATSC SDP,LSID and/or CMT.

The USD may include transport path information for the full MPD and/orATSC SDP.

The USD may include the broadcastAppService element for mobile broadcastnetworks, the unicastAppService element for the Internet and/or theatscAppService element for normal broadcast networks.

The broadcastAppService element may specify “UHD video component” andthe basePattern element may specify “basePattern1”.

The unicastAppService element may specify a second audio component andthe basePattern element may specify “basePattern4”.

The atscAppService element may include a first atscAppService elementfor an HD video component and a second atscAppService element for afirst audio component. The first atscAppService element may indicate “HDvideo component”, the basePattern attribute may indicate “basePattern2”and the DP_ID attribute may specify “DP_id3”. The second atscAppServiceelement may indicate “first audio component”, the basePattern attributemay indicate “basePattern3” and the DP_ID attribute may specify“DP_id3”.

The ATSC SDP may include information about at least one ROUTE sessionfor a service and/or a component included in the service.

The full MPD may include information about the UHD video componenthaving segment URL information of “basePattern1”. In addition, the fullMPD may include information about the HD video component having segmentURL information (or representation ID information) of “basePattern2”.Furthermore, the full MPD may include information about the first audiocomponent having segment URL information (or representation IDinformation) of “basePattern3”. The full MPD may include informationabout the second audio component having segment URL information of“basePattern4”.

The LSID may be acquired on the basis of information about ROUTEsessions.

The CMT may include a BroadcastComp element containing mappinginformation of components transmitted through a broadcast network. Forexample, the BroadcastComp element can include a first BroadcastCompelement containing mapping information of the HD video componenttransmitted through the broadcast network and/or a second BroadcastCompelement containing mapping information of the first audio componenttransmitted through the broadcast network. Each of the firstBroadcastComp element and the second BroadcastComp element may include aRep_ID attribute which indicates a DASH representation ID associatedwith the corresponding component and/or a DP_ID attribute whichindicates the ID of a DP (or PLP) through which the correspondingcomponent data is transmitted in the corresponding broadcast stream. TheRep_ID attribute of the first BroadcastComp element may indicate“rep_id2” and the DP_ID attribute thereof may indicate “DP_id2”. TheRep_ID attribute of the second BroadcastComp element may indicate“rep_id3” and the DP_ID attribute thereof may indicate “DP_id3”.

Referring to FIG. 50(b), a broadcast transmission apparatus(broadcaster) C500200 according to the third embodiment of the presentinvention may transmit service data and/or signaling data for servicesusing normal broadcast networks and/or the Internet. For example, thebroadcaster C500200 can transmit service data and/or signaling data forservices through a normal broadcast network using a first broadcasttransmission apparatus (not shown). The broadcaster C500200 can transmitservice data and/or signaling data for services over the Internet usinga content server (not shown). A second broadcast transmission apparatus(mobile carrier) C500300 may transmit service data and/or signaling datafor services using a mobile broadcast network (e.g. LTE broadcast).

The first broadcast transmission apparatus may transmit a videocomponent and a first audio component of a base layer for a serviceusing a normal broadcast network. For example, the video component ofthe base layer can be an HD video component. Information about a paththrough which the HD video component is transmitted can be“basePattern2” and information about a path through which the firstaudio component is transmitted can be “basePattern3”. In addition, theHD video component and/or the first audio component can be transmittedthrough a predetermined data pipe (DP) and/or a physical layer pipe(PLP). For example, the predetermined DP has an identifier of “DP_id3”.

The content server may transmit a second audio component for the serviceusing the Internet. For example, information on the path through whichthe second audio component is transmitted can be “basePattern4”.

The second broadcast transmission apparatus C500300 may transmit a videocomponent of an enhanced layer for the service using a mobile broadcastnetwork (LTE broadcast). For example, the video component of theenhanced layer can be a UHD video component. The video component of theenhanced layer may be additional information for generating UHD video.In addition, information on the path through which the UHD videocomponent is transmitted may be “basePattern1”.

A broadcast reception apparatus C500500 according to the thirdembodiment of the present invention may receive service data and/orsignaling data for services. The broadcast reception apparatus C500500may receive the HD video component and/or the first audio component fromthe broadcast transmission apparatus C500200 using a broadcast receiver.The broadcast reception apparatus C500500 may receive the second audiocomponent from the broadcast transmission apparatus C500200 using an IPtransceiver. The broadcast reception apparatus C500500 may receive theUHD video component from the second broadcast transmission apparatusC500300 using the broadcast receiver. The broadcast reception apparatusC500500 may acquire the HD video component, the first audio component,the second audio component and/or the UHD video component on the basisof the capability and environment thereof and decode and/or reproducethe acquired data.

The broadcast reception apparatus C500500 according to the thirdembodiment of the present invention may acquire the HD video componentand/or the first audio component on the basis of the CMT includingmapping information of components transmitted through a broadcastnetwork.

FIG. 51 illustrates a configuration of signaling data according to afourth embodiment of the present invention.

The signaling data according to the fourth embodiment may include lowlevel signaling data and/or service layer signaling data. The signalingdata according to the fourth embodiment of the present invention isapplicable even to a mobile environment.

According to the fourth embodiment of the present invention, SSCbootstrapping information may be transmitted through the low levelsignaling data. Signaling data associated with a service may betransmitted through USD of the service layer signaling data andsignaling data associated with a component may be transmitted through aCMT of the service layer signaling data.

The fourth embodiment of the present invention can provide a servicesignaling method for services transmitted through mobile broadcastnetworks (LTE broadcast), the Internet (unicast) and/or normal broadcastnetworks (ATSC broadcast or DVB broadcast) by extending 3GPP USD.

The SSC bootstrapping information is transmitted through an FIC and anSSC delivered through the SSC bootstrapping information includes USD.

A description will be given of USD extension according to the fourthembodiment of the present invention.

FIG. 51(a) illustrates the low level signaling data according to thefourth embodiment of the present invention.

The low level signaling data is signaling information supportingbootstrapping of fast channel scan and service acquisition by areceiver. For example, the low level signaling data can include a fastinformation channel (FIC) and/or rating region description (RRD).

The contents of the low level signaling data according to the fourthembodiment of the present invention can include the contents of theaforementioned low level signaling data.

FIG. 51(b) illustrates the service layer signaling data according to thefourth embodiment of the present invention.

The contents of the low level signaling data according to the fourthembodiment of the present invention can include the contents of theaforementioned low level signaling data. The following description isbased on a difference between the low level signaling data according tothe third embodiment of the present invention and the aforementioned lowlevel signaling data.

The service layer signaling data may include USD, AppSvc MPD, eMBMS MPDand/or 3GPP SDP. In addition, the service layer signaling data mayinclude full MPD, ATSC SDP, CMT and/or LSID. The AppSvc MPD, eMBMS MPDand/or 3GPP SDP may be signaling data for mobile broadcast networks. TheUSD, full MPD, ATSC SDP, CMT and/or LSID may be signaling data fornormal broadcast networks.

The USD may include a deliveryMethod element and/or anatscServiceDescription element.

The deliveryMethod element may include a broadcastAppService element formobile broadcast networks, a unicastAppService element for the Internetand/or an atscAppService element for normal broadcast networks.

Each of the broadcastAppService element and/or the unicastAppServiceelement may include a basePattern element. The basePattern element mayrefer to information about a segment URL to which each component ismapped in MPD.

The atscAppService element may include a Rep_ID attribute whichindicates the ID of DASH representation associated with thecorresponding component in MPD.

The CMT may include component related information such as componentinformation (associated DASH representation information) for a serviceand a path through which the corresponding component can be acquired.

For example, the CMT can include a Rep_ID attribute which indicates theID of DASH representation associated with the corresponding component inMPD.

In addition, the CMT may include the ID (DP ID attribute or PLP IDattribute) of a physical layer pipe (data pipe) through which componentdata for a service is transmitted.

A broadcast reception apparatus according to the fourth embodiment ofthe present invention can acquire a service on the basis of signalingdata. Specifically, the broadcast reception apparatus can acquire lowlevel signaling data and acquire service layer signaling data on thebasis of the low level signaling data. Then, the broadcast receptionapparatus can determine properties of a service using service layersignaling data (USD). Subsequently, the broadcast reception apparatuscan select at least one component for the service using service layersignaling data (MPD). For example, the broadcast reception apparatus canselect at least one component for the service using at least onerepresentation ID of the MPD. Then, the broadcast reception apparatuscan acquire information on a transport path through which the selectedat least one component is transmitted using service layer signaling data(SDP, CMT and/or LSID).

FIG. 52 illustrates a service according to the fourth embodiment of thepresent invention.

FIG. 52(a) shows signaling data according to the fourth embodiment ofthe present invention. The signaling data may be transmitted by thefirst broadcast transmission apparatus. However, the present inventionis not limited thereto and the signaling data may be transmitted by thesecond broadcast transmission apparatus and/or the content server.

The signaling data may include low level signaling data and/or servicelayer signaling data. The contents of the signaling data according tothe fourth embodiment of the present invention may include the contentsof the aforementioned signaling data. The following description is basedon a difference between the signaling data according to the fourthembodiment of the present invention and the aforementioned signalingdata.

The service layer signaling data may include USD, full MPD, ATSC SDP,LSID and/or CMT.

The USD may include transport path information for the full MPD and/orATSC SDP.

The USD may include the broadcastAppService element for mobile broadcastnetworks, the unicastAppService element for the Internet and/or theatscAppService element for normal broadcast networks.

The broadcastAppService element may specify “UHD video component” andthe basePattern element may specify “basePattern1”.

The unicastAppService element may specify a second audio component andthe basePattern element may specify “basePattern4”.

The atscAppService element may include a first atscAppService elementfor an HD video component and a second atscAppService element for afirst audio component.

Each of the first atscAppService element and/or the secondatscAppService element may include a Rep_ID attribute which indicates aDASH representation ID associated with the corresponding componentand/or a CMT_URL attribute which indicates a CMT transport path.

The first atscAppService element may indicate “HD video component” andthe Rep_ID attribute may indicate “rep_id2”. The second atscAppServiceelement may indicate “first audio component” and the Rep_ID attributemay indicate “rep_id3”.

The ATSC SDP may include information about at least one ROUTE sessionfor a service and/or a component included in the service.

The full MPD may include information about the UHD video componenthaving segment URL information of “basePattern1”. In addition, the fullMPD may include information about the HD video component havingrepresentation ID information of “rep_id2”. Furthermore, the full MPDmay include information about the first audio component havingrepresentation ID information) of “rep_id3”. The full MPD may includeinformation about the second audio component having segment URLinformation of “basePattern4”.

The LSID may be acquired on the basis of information about a ROUTEsession.

The CMT may include a BroadcastComp element containing mappinginformation of components transmitted through a broadcast network. Forexample, the BroadcastComp element can include a first BroadcastCompelement containing mapping information of the HD video componenttransmitted through the broadcast network and/or a second BroadcastCompelement containing mapping information of the first audio componenttransmitted through the broadcast network. Each of the firstBroadcastComp element and the second BroadcastComp element may include aRep_ID attribute which indicates a DASH representation ID associatedwith the corresponding component and/or a DP_ID attribute whichindicates the ID of a DP (or PLP) through which the correspondingcomponent data is transmitted in a broadcast stream. The Rep_IDattribute of the first BroadcastComp element may indicate “rep_id2” andthe DP_ID attribute thereof may indicate “DP_id2”. The Rep_ID attributeof the second BroadcastComp element may indicate “rep_id3” and the DP_IDattribute thereof may indicate “DP_id3”.

Referring to FIG. 52(b), a broadcast transmission apparatus(broadcaster) C520200 according to the fourth embodiment of the presentinvention may transmit service data and/or signaling data for servicesusing normal broadcast networks and/or the Internet. For example, thebroadcaster C520200 can transmit service data and/or signaling data forservices through a normal broadcast network using a first broadcasttransmission apparatus (not shown). The broadcaster C520200 may transmitservice data and/or signaling data for services over the Internet usinga content server (not shown). A second broadcast transmission apparatus(mobile carrier) C520300 may transmit service data and/or signaling datafor services using a mobile broadcast network (e.g. LTE broadcast).

The first broadcast transmission apparatus may transmit a videocomponent and a first audio component of a base layer for a serviceusing a normal broadcast network. For example, the video component ofthe base layer can be an HD video component. The HD video component canbe matched to “Rep_id2” of MPD and the first audio component can bematched to “Rep_id3” of the MOD. In addition, the HD video componentand/or the first audio component can be transmitted through apredetermined DP and/or a PLP. For example, the predetermined DP has anidentifier of “DP_id3”.

The content server may transmit a second audio component for the serviceusing the Internet. For example, information on the path through whichthe second audio component is transmitted can be “basePattern4”.

The second broadcast transmission apparatus C520300 may transmit a videocomponent of an enhanced layer for the service using a mobile broadcastnetwork (LTE broadcast). For example, the video component of theenhanced layer can be a UHD video component. The video component of theenhanced layer may be additional information for generating UHD video.In addition, information on the path through which the UHD videocomponent is transmitted can be “basePattern1”.

A broadcast reception apparatus C520500 according to the fourthembodiment of the present invention may receive service data and/orsignaling data for services. The broadcast reception apparatus C520500may receive the HD video component and/or the first audio component fromthe broadcast transmission apparatus C520200 using a broadcast receiver.The broadcast reception apparatus C520500 may receive the second audiocomponent from the broadcast transmission apparatus C520200 using an IPtransceiver. The broadcast reception apparatus C520500 may receive theUHD video component from the second broadcast transmission apparatusC520300 using the broadcast receiver. The broadcast reception apparatusC520500 may acquire the HD video component, the first audio component,the second audio component and/or the UHD video component on the basisof the capability and environment thereof and decode and/or reproducethe acquired data.

The broadcast reception apparatus C520500 according to the fourthembodiment of the present invention may acquire the HD video componentand/or the first audio component on the basis of the CMT includingmapping information of components transmitted through a broadcastnetwork.

FIG. 53 illustrates a configuration of signaling data according to afifth embodiment of the present invention.

The signaling data according to the fifth embodiment may include lowlevel signaling data and/or service layer signaling data. The signalingdata according to the fifth embodiment of the present invention isapplicable even to a mobile environment.

According to the fifth embodiment of the present invention, SSCbootstrapping information may be transmitted through the low levelsignaling data. Signaling data associated with a service may betransmitted through USD of the service layer signaling data andsignaling data associated with components transmitted through allnetworks may be transmitted through a CMT of the service layer signalingdata.

The fifth embodiment of the present invention can provide a servicesignaling method for services transmitted through mobile broadcastnetworks (LTE broadcast), the Internet (unicast) and/or normal broadcastnetworks (ATSC broadcast or DVB broadcast) by extending the CMT.

The SSC bootstrapping information is transmitted through an FIC and anSSC delivered through the SSC bootstrapping information includes USD.

A description will be given of CMT extension according to the fifthembodiment of the present invention.

FIG. 53(a) illustrates the low level signaling data according to thefifth embodiment of the present invention.

The low level signaling data is signaling information supportingbootstrapping of fast channel scan and service acquisition by areceiver. For example, the low level signaling data can include a fastinformation channel (FIC) and/or rating region description (RRD).

The contents of the low level signaling data according to the fifthembodiment of the present invention can include the contents of theaforementioned low level signaling data.

FIG. 53(b) illustrates the service layer signaling data according to thefifth embodiment of the present invention.

The contents of the low level signaling data according to the fifthembodiment of the present invention can include the contents of theaforementioned low level signaling data. The following description isbased on a difference between the low level signaling data according tothe fifth embodiment of the present invention and the aforementioned lowlevel signaling data.

The service layer signaling data may include USD, full MPD, ATSC SDP,CMT and/or LSID. The USD, full MPD, ATSC SDP, CMT and/or LSID may besignaling data for normal broadcast networks.

The CMT may include component related information such as componentinformation (associated DASH representation information) for a serviceand a path through which the corresponding component can be acquired.

The CMT may include a BroadcastComp element containing informationassociated with a component transmitted through a normal broadcastnetwork (ATST broadcast or DVB broadcast), a BBComp element containinginformation associated with a component transmitted over the Internetand/or an eMBMSComp element containing information associated with acomponent transmitted through a mobile broadcast network (LTEbroadcast).

Each of the BroadcastComp element, the BBComp element and/or theeMBMSComp element may include a Rep_ID attribute which indicates the IDof DASH representation associated with the corresponding component.

In addition, each of the BroadcastComp element, the BBComp elementand/or the eMBMSComp element may include a DP_ID attribute (or PLP_IDattribute) which indicates the ID of a physical layer pipe (data pipe)through which component data for a service is transmitted.

A broadcast reception apparatus according to the fifth embodiment of thepresent invention can acquire a service on the basis of signaling data.Specifically, the broadcast reception apparatus can acquire low levelsignaling data and acquire service layer signaling data on the basis ofthe low level signaling data. Then, the broadcast reception apparatuscan determine properties of a service using service layer signaling data(USD). Subsequently, the broadcast reception apparatus can select atleast one component for the service using service layer signaling data(MPD). For example, the broadcast reception apparatus can select atleast one component for the service using at least one representation IDof the MPD. Then, the broadcast reception apparatus can acquireinformation on a transport path through which the selected at least onecomponent is transmitted using service layer signaling data (SDP, CMTand/or LSID).

FIG. 54 illustrates a service according to the fifth embodiment of thepresent invention.

FIG. 54(a) shows signaling data according to the fifth embodiment of thepresent invention. The signaling data may be transmitted by the firstbroadcast transmission apparatus. However, the present invention is notlimited thereto and the signaling data may be transmitted by the secondbroadcast transmission apparatus and/or the content server.

The signaling data may include low level signaling data and/or servicelayer signaling data. The contents of the signaling data according tothe fifth embodiment of the present invention may include the contentsof the aforementioned signaling data. The following description is basedon a difference between the signaling data according to the fifthembodiment of the present invention and the aforementioned signalingdata.

The service layer signaling data may include USD, full MPD, ATSC SDP,LSID and/or CMT.

The USD may include transport path information for the full MPD and/orATSC SDP.

The USD may include the broadcastAppService element for mobile broadcastnetworks, the unicastAppService element for the Internet and/or theatscAppService element for normal broadcast networks.

The broadcastAppService element may specify “UHD video component”. TheunicastAppService element may specify a second audio component. TheatscAppService element may include a first atscAppService element for anHD video component and a second atscAppService element for a first audiocomponent. The first atscAppService element may indicate “HD videocomponent”. The second atscAppService element may indicate “first audiocomponent”.

The ATSC SDP may include information about at least one ROUTE sessionfor a service and/or a component included in the service.

The full MPD may include information about the UHD video componenthaving representation ID information of “rep_id1”. In addition, the fullMPD may include information about the HD video component havingrepresentation ID information of “rep_id2”. Furthermore, the full MPDmay include information about the first audio component havingrepresentation ID information) of “rep_id3”. The full MPD may includeinformation about the second audio component having representation IDinformation of “rep_id4”.

The LSID may be acquired on the basis of information about ROUTEsessions.

The CMT may include a BroadcastComp element containing informationrelated to a component transmitted through a normal broadcast network(ATSC broadcast or DVB broadcast), a BBComp element containinginformation associated with a component transmitted over the Internetand/or an eMBMSComp element containing information associated with acomponent transmitted through a mobile broadcast network (LTEbroadcast).

For example, the BroadcastComp element can include a first BroadcastCompelement containing mapping information of the HD video componenttransmitted through a normal broadcast network and/or a secondBroadcastComp element containing mapping information of the first audiocomponent transmitted through the normal broadcast network. Each of thefirst BroadcastComp element and the second BroadcastComp element mayinclude a Rep_ID attribute which indicates a DASH representation IDassociated with the corresponding component and/or a DP_ID attributewhich indicates the ID of a DP (or PLP) through which the correspondingcomponent data is transmitted in a broadcast stream. The Rep_IDattribute of the first BroadcastComp element may indicate “rep_id2” andthe DP_ID attribute thereof may indicate “DP_id2”. The Rep_ID attributeof the second BroadcastComp element may indicate “rep_id3” and the DP_IDattribute thereof may indicate “DP_id3”.

The BBComp element may include mapping information of the second audiocomponent transmitted over the Internet (unicast). The Rep_ID attributeof the BBComp element may indicate “rep_id4”.

The eMBMSComp element may include mapping information of the UHD videocomponent transmitted through a mobile broadcast network (LTEbroadcast). The Rep_ID attribute of the eMBMSComp element may indicate“rep_id1”.

Referring to FIG. 54(b), a broadcast transmission apparatus(broadcaster) C540200 according to the fifth embodiment of the presentinvention may transmit service data and/or signaling data for servicesusing normal broadcast networks and/or the Internet. For example, thebroadcaster C540200 can transmit service data and/or signaling data forservices through a normal broadcast network using a first broadcasttransmission apparatus (not shown). The broadcaster C540200 may transmitservice data and/or signaling data for services over the Internet usinga content server (not shown). A second broadcast transmission apparatus(mobile carrier) C540300 may transmit service data and/or signaling datafor services using a mobile broadcast network (e.g. LTE broadcast).

The first broadcast transmission apparatus may transmit a videocomponent and a first audio component of a base layer for a serviceusing a normal broadcast network. For example, the video component ofthe base layer can be an HD video component. The HD video component canbe matched to “Rep_id2” of MPD and the first audio component can bematched to “Rep_id3” of the MOD. In addition, the HD video componentand/or the first audio component can be transmitted through apredetermined DP and/or a PLP. For example, the predetermined DP has anidentifier of “DP_id3”.

The content server may transmit a second audio component for the serviceusing the Internet. For example, the second audio component can bematched to “Rep_id4” of MPD.

The second broadcast transmission apparatus C540300 may transmit a videocomponent of an enhanced layer for the service using a mobile broadcastnetwork (LTE broadcast). For example, the video component of theenhanced layer can be a UHD video component. The video component of theenhanced layer may be additional information for generating UHD video.In addition, the UHD video component can be matched to “Rep_id1” of theMPD.

A broadcast reception apparatus C540500 according to the fifthembodiment of the present invention may receive service data and/orsignaling data for services. The broadcast reception apparatus C540500may receive the HD video component and/or the first audio component fromthe broadcast transmission apparatus C540200 using a broadcast receiver.The broadcast reception apparatus C540500 may receive the second audiocomponent from the broadcast transmission apparatus C540200 using an IPtransceiver. The broadcast reception apparatus C540500 may receive theUHD video component from the second broadcast transmission apparatusC540300 using the broadcast receiver. The broadcast reception apparatusC540500 may acquire the HD video component, the first audio component,the second audio component and/or the UHD video component on the basisof the capability and environment thereof and decode and/or reproducethe acquired data.

The broadcast reception apparatus C540500 according to the fifthembodiment of the present invention may acquire the HD video component,the first audio component, the second audio component and/or the UHDvideo component on the basis of the CMT including mapping information ofcomponents transmitted through a broadcast network, and decode/reproducethe acquired data.

FIG. 55 illustrates a configuration of signaling data according to asixth embodiment of the present invention.

The signaling data according to the sixth embodiment may include lowlevel signaling data and/or service layer signaling data. The signalingdata according to the sixth embodiment of the present invention isapplicable even to a mobile environment.

According to the sixth embodiment of the present invention, SSCbootstrapping information may be transmitted through the low levelsignaling data. Signaling data associated with a service may betransmitted through USD of the service layer signaling data andsignaling data associated with a component may be transmitted through aCMT of the service layer signaling data.

The sixth embodiment of the present invention can provide a servicesignaling method for services transmitted through mobile broadcastnetworks (LTE broadcast), the Internet (unicast) and/or normal broadcastnetworks (ATSC broadcast or DVB broadcast) by extending 3GPP SDP.

The SSC bootstrapping information is transmitted through an FIC and anSSC delivered through the SSC bootstrapping information includes USD.

A description will be given of SDP extension according to the sixthembodiment of the present invention.

FIG. 55(a) illustrates the low level signaling data according to thesixth embodiment of the present invention.

The low level signaling data is signaling information supportingbootstrapping of fast channel scan and service acquisition by areceiver. For example, the low level signaling data can include an FICand/or RRD.

The contents of the low level signaling data according to the sixthembodiment of the present invention can include the contents of theaforementioned low level signaling data.

FIG. 55(b) illustrates the service layer signaling data according to thesixth embodiment of the present invention.

The contents of the low level signaling data according to the sixthembodiment of the present invention can include the contents of theaforementioned low level signaling data. The following description isbased on a difference between the low level signaling data according tothe sixth embodiment of the present invention and the aforementioned lowlevel signaling data.

The service layer signaling data may include USD, AppSvc MPD, eMBMS MPDand/or 3GPP SDP. In addition, the service layer signaling data mayinclude SDP, CMT and/or LSID. The AppSvc MPD, eMBMS MPD, 3GPP SDP, SDP,CMT and/or LSID may be signaling data for normal broadcast networks andthe Internet as well as mobile broadcast networks.

The USD may include path information for the AppAvc MPD, eMBMS MPDand/or 3GPP SDP.

The 3GPP SDP may include at least one ROUTE session element whichprovides information about at least one ROUTE for a service and/or acomponent included in the service. The ROUTE session element may includetransport path information for a ROUTE session. For example, the ROUTEsession element can include a bsid attribute which indicates the ID of abroadcast stream through which a content component of the service istransmitted, an sIpAddr attribute which indicates the source IP addressof the ROUTE session, a dIpAddr attribute which indicates thedestination IP address of the ROUTE session, a dport attribute whichindicates the destination port number of the ROUTE session and/or aPLPID attribute which indicates a physical layer parameter for the ROUTEsession. The bsid attribute, sIpAddr attribute, dIpAddr attribute, dportattribute and/or PLPID attribute can be used as information on atransport path through which LSID is transmitted.

In addition, the 3GPP SDP may include at least one LCT session elementwhich provides information about at least one LCT session for a serviceand/or a component included in the service. For reference, a ROUTEsession can include at least one LCT session. For example, the LCTsession element can include a tsi attribute which indicates the ID ofthe corresponding LCT session and/or a PLPID attribute which indicates aphysical layer parameter for the corresponding LCT session.

The CMT may include component related information such as componentinformation (associated DASH representation information) for a serviceand a path through which the corresponding component can be acquired.

For example, the CMT can include the ID (DP ID attribute or PLP IDattribute) of a physical layer pipe (data pipe) through which componentdata for a service is transmitted.

The LSID may include information for specifying a transport sessionthrough which a component for a service is transmitted. The LSID may beincluded in each ROUTE session. The LSID may be transmitted through aspecific transport session in the corresponding ROUTE session. Inaddition, the LSID may include information about an LCT session includedin the ROUTE session. For example, the LSID can include a tsi attributewhich specifies a transport session through which a content componentfor a service is transmitted.

The SPD (or service configuration description (SCD)) may include avariety of additional signaling information which is not included in thelow level signaling data (or FIC).

A broadcast reception apparatus according to the sixth embodiment of thepresent invention can acquire a service on the basis of signaling data.Specifically, the broadcast reception apparatus can acquire low levelsignaling data and acquire service layer signaling data on the basis ofthe low level signaling data. Then, the broadcast reception apparatuscan determine properties of a service using service layer signaling data(USD and/or SPD). Subsequently, the broadcast reception apparatus canselect at least one component for the service using service layersignaling data (MPD). For example, the broadcast reception apparatus canselect at least one component for the service using at least onerepresentation ID of the MPD. Then, the broadcast reception apparatuscan acquire information on a transport path through which the selectedat least one component is transmitted using service layer signaling data(SDP, CMT and/or LSID).

The broadcast reception apparatus according to the sixth embodiment ofthe present invention may acquire transport path information of at leastone component using the LSID, CMT and/or SDP (ROUTE session element).

In addition, the broadcast reception apparatus according to the sixthembodiment of the present invention may acquire transport pathinformation of at least one component using the LSID and/or SDP (LCTsession element). In this case, the tsi attribute which specifies an LCTsession may be present in both the LSID and SDP (LCT session element).In addition, the broadcast reception apparatus may acquire the transportpath information of the at least one component without using the CMT.

FIG. 56 illustrates effects of signaling according to the first to sixthembodiments of the present invention.

The first embodiment of the present invention can achieve separatesignaling for mobile broadcast networks (3GPP) and normal broadcastnetworks (ATSC or DVB). In addition, signaling according to the firstembodiment of the present invention can have extensibility. However,signaling according to the first embodiment of the present invention maybe duplication for components transmitted over the Internet.Furthermore, the structure of signaling according to the firstembodiment has complexity.

Signaling according to the second embodiment of the present inventiondoes not require the CMT. In addition, signaling according to the secondembodiment of the present invention has a less complex structure thansignaling according to the first embodiment of the present invention.Furthermore, the second embodiment of the present invention can achieveseparate signaling for mobile broadcast networks (3GPP) and normalbroadcast networks (ATSC or DVB) using the extended USD. However,signaling according to the second embodiment of the present inventionmay cause eMBMS signaling layering violation.

Signaling according to the third and fourth embodiments of the presentinvention does not cause layering violation for USD extension. Inaddition, the third and fourth embodiments of the present invention canachieve separate signaling for mobile broadcast networks (3GPP) andnormal broadcast networks (ATSC or DVB) using the extended USD. However,in the signaling according to the third and fourth embodiments of thepresent invention, an optional attribute should be used in the CMT.

Signaling according to the fifth embodiment of the present invention hassimplest structure. In addition, signaling according to the fifthembodiment of the present invention does not cause layering violation.

Signaling according to the sixth embodiment of the present invention canhave extensibility since the signaling uses the extended SPD. However,signaling according to the sixth embodiment of the present invention mayhave a complex structure.

FIG. 57 is a flowchart illustrating a broadcast transmission methodaccording to an embodiment of the present invention.

A broadcast transmission apparatus may generate service data for aservice using a controller (not shown) (CS570100).

The broadcast transmission apparatus may generate service layersignaling data using the controller (CS570200).

The broadcast transmission apparatus may transmit a broadcast signalincluding the service data and the service layer signaling data using atransmitter (CS570300).

The service layer signaling data may include first signaling data,second signaling data and third signaling data. For example, the firstsignaling data can include the aforementioned USD, SPD and/or SMT.

The first signaling data may include reference information for referringto the second signaling data and the third signaling data.

The second signaling data may include description for a component of theservice. For example, the second signaling data can include theaforementioned AppSvc MPD, eMBMS MPD and/or full MPD.

The third signaling data may include information for acquiring thecomponent associated with the service. For example, the third signalingdata can include the aforementioned 3GPP SDP, SMT, CMT, ATSC SDP, UST,RRD, ROUTE session element, LCT session element and/or LSID.

The broadcast transmission apparatus may generate low level signalingdata using the controller. The low level signaling data may supportbootstrapping of service acquisition. For example, the low levelsignaling data can include the aforementioned FIC, UST and/or RRD.

The broadcast transmission apparatus may transmit a broadcast signalincluding the service data, the service layer signaling data and the lowlevel signaling data using the transmitter.

The reference information may include first reference information forreferring to the second signaling data and second reference informationfor referring to the third signaling data. For example, the firstreference information can correspond to the aforementioned Full_MPD_URLattribute and the second reference information can correspond to theaforementioned ATSC_SDP_URL attribute.

The first signaling data may further include capability informationwhich specifies capabilities necessary for reproduction of the service.For example, the capability information can correspond to theaforementioned Capabilities attribute.

The third signaling data may include a first transport session elementand a second transport session element. The first transport sessionelement may include information about a first transport session throughwhich the service is transmitted. The second transport session elementmay include information about a second transport session through whichthe component of the service is transmitted. For example, the firsttransport session can be a ROUTE session and the second transportsession can be an LCT session.

The third signaling data may include at least one of a PLPID attributewhich specifies a physical layer pipe through which the component istransmitted and a tsi attribute which specifies the second transportsession.

The third signaling data may include mapping information which is mappedto the service transmitted through the second transport session. Forexample, the mapping information can correspond to the aforementionedRep_id attribute.

The mapping information may be a representation ID of dynamic adaptivestreaming over HTTP (DASH) content for selecting the second transportsession.

FIG. 58 is a flowchart illustrating a broadcast reception methodaccording to an embodiment of the present invention.

A broadcast reception apparatus may receive a broadcast signal includingservice data and service layer signaling data for a service using abroadcast receiver (SC580100).

The broadcast reception apparatus may acquire the service layersignaling data using a controller (CS580200).

The broadcast reception apparatus may discover and/or acquire acomponent of the service on the basis of the service layer signalingdata using the controller (CS580300).

In addition, the broadcast reception apparatus may acquire low levelsignaling data using the controller. The low level signaling data maysupport bootstrapping of service acquisition.

The service layer signaling data may include first signaling data,second signaling data and third signaling data. The first signaling datamay include reference information for referring to the second signalingdata and the third signaling data. The second signaling data may includedescription for a component of the service. The third signaling data mayinclude information for acquiring the component associated with theservice.

The reference information may include first reference informationreferring to the second signaling data and second reference informationreferring to the third signaling data. The first signaling data mayfurther include capability information which specifies capabilitiesnecessary for reproduction of the service.

The third signaling data may include a first transport session elementand a second transport session element. The first transport sessionelement may include information about a first transport session throughwhich the service is transmitted. The second transport session elementmay include information about a second transport session through whichthe component of the service is transmitted.

The third signaling data may include at least one of a PLPID attributewhich specifies a physical layer pipe through which the component istransmitted and a tsi attribute which specifies the second transportsession.

The third signaling data may include mapping information which is mappedto the service transmitted through the second transport session. Themapping information may be a representation ID of DASH content forselecting the second transport session.

FIG. 59 illustrates a configuration of signaling data according to aseventh embodiment of the present invention.

The signaling data according to the seventh embodiment may include lowlevel signaling data and/or service layer signaling data. The signalingdata according to the seventh embodiment of the present invention isapplicable even to a mobile environment.

The signaling data according to the seventh embodiment of the presentinvention may provide ATSC broadcast service signaling by extendingservice description, session description and a file delivery overunidirectional transport (FLUTE) based object extension transportscheme.

According to the seventh embodiment of the present invention, SSCbootstrapping information may be transmitted through the low levelsignaling data. Signaling data associated with a service and signalingdata associated with a component may be transmitted through USD of theservice layer signaling data.

The seventh embodiment of the present invention can provide a servicesignaling method for services transmitted through mobile broadcastnetworks (LTE broadcast), the Internet (unicast) and/or normal broadcastnetworks (ATSC broadcast or DVB broadcast).

The SSC bootstrapping information may be transmitted through an FIC. AnSSC can include USD, AppSvc MPD, eMBMS MPD, 3GPP SDP, ATSC SDP and/orfull MPD.

A description will be given of methods of extending USD, SDP and/or LSIDaccording to the seventh embodiment of the present invention.

The low level signaling data is signaling information supportingbootstrapping of fast channel scan and service acquisition by areceiver. Bootstrapping of service acquisition may refer to a procedurefor acquiring a service. Accordingly, information for bootstrapping mayinclude path information for acquiring the service. For example, the lowlevel signaling data can include an FIC and/or RRD.

The FIC may be referred to as a service list table (SLT). The SLT mayinclude service layer signaling (SLS) bootstrapping information. The SLSbootstrapping information may include service signaling channel (SSC)bootstrapping information for at least one service.

For example, the SSC can be a channel through which the SLS and/orservice layer signaling data is transmitted. SSC bootstrapping may referto a procedure for acquiring the SSC (or service layer signaling data).Accordingly, the SSC bootstrapping information can include pathinformation for acquiring the service layer signaling data.

The contents of the low level signaling data according to the seventhembodiment of the present invention can include the contents of theaforementioned low level signaling data.

The contents of the service layer signaling data according to theseventh embodiment of the present invention can include the contents ofthe aforementioned service layer signaling data. The followingdescription is based on a difference between the service layer signalingdata according to the seventh embodiment of the present invention andthe aforementioned service layer signaling.

The service layer signaling data may include USD, AppSvc MPD, eMBMS MPDand/or 3GPP SDP. In addition, the service layer signaling data mayinclude ATSC SDP, full MPD and/or LSID. The service layer signaling datamay include a plurality of ATSC SDPs. The USD, AppSvc MPD, eMBMS MPD,3GPP SDP, ATSC SDP, full MPD and/or LSID may be signaling data fornormal broadcast networks and/or the Internet as well as mobilebroadcast networks.

The USD may include transport path information for the AppSvc MPD, eMBMSMPD and/or 3GPP SDP.

In addition, the USD may include an atscServiceDescription elementcontaining attributes of a service and/or information about a paththrough which the service can be acquired. For example, theatscServiceDescription element can include information about a paththrough which the ATSC SDP can be acquired.

The USD may include a DeliveryMethod element which indicates a containerof transport related information associated with service contenttransmitted through a broadcast access mode and/or a broadband accessmode. For example, the DeliveryMethod element can include anatscAppService element for normal broadcast networks. The atscAppServiceelement can include a basePattern element containing unique mappinginformation of a component transmitted through the atscAppServiceelement.

Furthermore, the USD may include an appService element containinginformation for mapping a component transmitted through a normalbroadcast network (ATSC broadcast or DVB broadcast) to mediapresentation description information of the corresponding component. Forexample, the appService element can include path information foracquiring the full MPD.

Each ATSC SDP may include at least one ROUTE session element whichprovides information about at least one ROUTE session for a serviceand/or a component included in the service. The ROUTE session elementmay include transport path information for the corresponding ROUTEsession. For example, the transport path information for the ROUTEsession can be used as information about a transport path through whichLSID is transmitted.

The LSID may include information about a transport session (LCT session)through which a component for a service is transmitted. The LSID may beincluded in each ROUTE session. The LSID may be transmitted through aspecific transport session included in the corresponding ROUTE session.

A broadcast reception apparatus according to the seventh embodiment ofthe present invention can acquire a service on the basis of signalingdata. Specifically, the broadcast reception apparatus can acquire lowlevel signaling data and acquire service layer signaling data on thebasis of the low level signaling data. Then, the broadcast receptionapparatus can determine properties of a service using service layersignaling data (USD). Subsequently, the broadcast reception apparatuscan select at least one component for the service using service layersignaling data (MPD). For example, the broadcast reception apparatus canselect at least one component for the service using at least onerepresentation ID of the MPD. Then, the broadcast reception apparatuscan acquire information on a transport path through which the selectedat least one component is transmitted using service layer signaling data(SDP and/or LSID).

FIG. 60 illustrates the USD according to the seventh embodiment of thepresent invention.

The extended USD according to the seventh embodiment of the presentinvention may include the atscServiceDescription element C600100,DeliveryMethod element C600200 and/or appService element C600300.

The atscServiceDescription element C600100 may include information abouta service transmitted through a normal broadcast network. TheatscServiceDescription element C600100 may include a ProtocolVersionattribute, an atscServiceId attribute, a GlobalServiceId attribute, anatscSdpURI element, a CapabilityDescription element, aTargetingDescription element, a ContentAdvisoryDescription elementand/or a ProgramTitleDescription element.

The atscSdpURI element according to the seventh embodiment of thepresent invention refers to information (URL information or URIinformation) which indicates an SDP (or ATSC SDP) including informationabout a ROUTE session through which a service (ATSC service or DVBservice) is transmitted. The atscSdpURI element refers to information(URL information or URI information) used to refer to S-TSID (orATSC_SDP) which provides access related parameters for transportsessions through which service content is transmitted.

Cardinality of the atscSdpURI element may be defined as 0 or unbounded.The SDP corresponding to the atscSdpURI element indicates a ROUTEsession which constitutes an ATSC service and describes sessiondescription information of the LSID. Accordingly, when the ATSC serviceis transmitted through one or more ROUTE sessions, as many atscSdpURIelements as the number of ROUTE sessions can be provided, and each URIindicates corresponding SDP data.

The contents of the atscServiceDescription element C600100 according tothe seventh embodiment of the present invention may include the contentsof the aforementioned atscServiceDescription element.

The DeliveryMethod element C600200 may be a container of transportrelated information associated with service content transmitted throughthe broadcast access mode and/or the broadband access mode. TheDeliveryMethod element C600200 may include an atscAppService element fornormal broadcast networks. The atscAppService element may includeinformation about DASH representation including configuration mediacontent components belonging to a service, which are transmitted througha normal broadcast network (ATSC broadcast or DVB broadcast) over allperiods of affiliated media presentation. For example, theatscAppService element can include information about data which uses theATSC broadcast delivery method. The atscAppService element can include abasePattern element. The basePattern element refers to segment URLinformation to which each component is mapped in MPD. For example, thebasePattern element can include unique mapping information of acomponent transmitted through the atscAppService element.

The appService element C600300 may indicate DASH representationincluding configuration media content components belonging to a service,which are transmitted through a normal broadcast network (ATSC broadcastor DVB broadcast) over all periods of affiliated media presentation. Forexample, the appService element C600300 can include information formapping a component transmitted through ATSC broadcast to mediapresentation description information of the corresponding component. TheappService element C600300 may include an identicalContent element, analternativeContent element, an appServiceDescriptionURI attribute and/ora mimeType attribute.

The appServiceDescription URI attribute refers to information (URLinformation or URI information) used to refer to MPD includinginformation about all content components of a service transmittedthrough a mobile broadcast network (LTE broadcast), the Internet and/ora normal broadcast network (ATSC broadcast or DVB broadcast).

FIG. 61 illustrates the ATSC SDP and/or the LSID according to theseventh embodiment of the present invention.

FIG. 61(a) shows the ATSC SDP according to the seventh embodiment of thepresent invention.

Definition of the ATSC SDP can be extended as follows. The ATSC SDP mayhave a unique URI value. For example, the ATSC SDP can have a URI valueof “sdpUri”. When FLUTE is used, the URI value can be designated throughContent-Location of an FDT. When ROUTE is used, the URI value can bedesignated through Content-Location described in an extended filedelivery table (EFDT). The URI value may have a unique value mapped toan atscSdpURI element value of the USD/atscServiceDescription.

The ATSC SDP may include component information (s), an originator andsession identifier (o), a source filter (a), connection information (c),media description (m), an ATSC mode (a, atsc-mode) and/or TSIinformation (a, route-tsi).

The component information (s) may include information about a component.For example, the component information (s) can have a value of“robust-audio”.

The originator and session identifier (o) may indicate the source IPaddress of a ROUTE session. For example, the originator and sessionidentifier (o) can be represented as “o=jdoe 2890844526 2890842807 INIP4 sourceIPaddress”.

The source filter (a) may indicate a source IP address. The sourcefilter (a) may be represented using “o=” or “source-filter attribute”.For example, the source filter (a) can be represented as “incl IN(Ipver) (sourceIPaddress)” and/or “incl IN IP6 * (sourceIPaddress)”.

The connection information (c) may indicate the destination IP addressof the ROUTE session. For example, the connection information (c) can berepresented as “IN IP4 destinationIPaddress”.

The media description (m) may indicate the destination port of the ROUTEsession. For example, the media description (m) can be represented asm=APPLICATION (destinationPort) ROUTE/UDP 0”.

The ATSC mode (a, atsc-mode) may indicate the ID of a transport streamthrough which LSID of the ROUTE session is transmitted and/or the ID ofa data pipe (or PLP) through which LSID of the ROUTE session istransmitted when the ATSC broadcast mode is used. For example, the atscmode (a) can be represented as “a=atsc-mode: transportstream_id, DP_id”.

The TSI information (a, route-tsi) may indicate the transport sessionidentifier of an LCT session through which the LSID of the ROUTE sessionis transmitted. This value is optionally described in the SDP andindicates transmission with “tsi 0” when the value is not described.When a specific tsi value is described, this value indicates that theLSID is transmitted with the described tsi. For example, the TSIinformation (a) can be represented as “a=route-tsi: tsi”.

FIG. 61(b) shows the LSID according to the seventh embodiment of thepresent invention.

The LSID may include information about an LCT session included in aROUTE session. For example, the LSID can include a version attribute, avalidFrom attribute, an expiration attribute and/or a TransportSessionelement.

The version attribute indicates the version of the LSID.

The validFrom attribute indicates time from which the LSID is valid.

The expiration attribute indicates time at which the LSID expires.

The TransportSession element may include information about one or moretransport sessions (or LCT sessions) which form a ROUTE session. Thetransport sessions (or LCT session) may be used to carry audio, videoand/or data and may be transmitted through the same data pipe (or PLP)or different data pipes (or PLPs). The LSID may be included in eachROUTE session. The LSID may be transmitted through a specific transportsession in the corresponding ROUTE session. For example, theTransportSession element may include a tsi attribute, a DP_id attribute,a SourceFlow element and/or a RepairFlow element.

The tsi attribute may specify a transport session through which acontent component for a service is transmitted.

The DP_id attribute may indicate the identifier of a physical layer pipe(or data pipe) associated with the transport session through which thecontent component for the service is transmitted. The DP_id attributemay indicate a data pipe (or physical layer pipe) through which thetransport session described in the corresponding LSID is transmitted.The DP_id is optionally described. If the corresponding DP_id is notpresent, this means that the transport session is transmitted throughthe data pipe having the same DP_id as the DP_id corresponding to theatsc mode value described in the ATSC SDP.

The SourceFlow element may include information about a source flowtransmitted through an LCT session. The source flow may carry sourcedata including a core component of ROUTE. For example, the source flowcan carry at least one delivery object through a unidirectional channel.

The RepairFlow element may include information about a repair flowtransmitted through an LCT session. The repair flow may carry repairdata which protects at least one delivery object.

FIG. 62 illustrates service layer signaling according to the seventhembodiment of the present invention.

A broadcast signal C620100 having a specific frequency may includeservice data and/or signaling data for a service. For example, thebroadcast signal C620100 can be identified by “BCStreamID1”.“BCStreamID1” can identify the broadcast signal in a specific areaand/or at the specific frequency.

The broadcast signal C620100 may include a first ROUTE session. Theservice data for the service may be transmitted through the first ROUTEsession. For example, the identifier of the service can have a value of“SrvcID1”.

The service data may include a video component and/or an audio componentfor the service. The video component may include at least one videosegment including video data. The audio component may include at leastone audio segment including audio data. The video component may betransmitted through a specific transport session of the first ROUTEsession. The audio component may be transmitted through anothertransport session of the first ROUTE session.

The signaling data may include low level signaling data and/or servicelayer signaling data. For example, the low level signaling data caninclude an FIC and/or an SLT. The low level signaling data may beincluded in an IP/UDP packet and transmitted. The service layersignaling data may be referred to as SLS. The service layer signalingdata may include USD, MPD (or full MPD), SDP (or ATSC SDP) and/or LSID.The USD, MPD and/or SDP may be transmitted through a service signalingchannel (SSC). The SSC and/or LSID may be transmitted through a specifictransport session of the first ROUTE session.

The first ROUTE session may be identified by a combination of a sourceIP address (sIPAdrs1), a destination IP address (IPAdrs1) and adestination port number (Port1). In addition, the first ROUTE sessionmay be transmitted through a first DP BaseBand Packet (BBP) SID1(BBPSID1) and/or a second DP (BBPSID2). Furthermore, the first ROUTEsession may include an SSC transport session (tsi-s), an LSID transportsession (tsi-0), a first transport session (tsi-v) and/or a secondtransport session (tsi-ra).

The SSC transport session (tsi-s) may include at least one SSC fragment.The at least one SSC fragment may be identified by a transport objectidentifier. For example, the transport object identifier for the SSCfragment can have a value of “toi-s-bundl”. The USD, MPD and/or SDP maybe transmitted through the SSC transport session.

The LSID transport session (tsi-0) may include at least one LSIDfragment. For example, a transport object identifier for the LSID canhave a value of “toi-0”. The LSID may be transmitted through the LSIDtransport session.

The first transport session (tsi-v) may include a video component. Forexample, the video component can include at least one video segment. Atransport object identifier for the video segment may have a specificvalue.

The second transport session (tsi-ra) may include an audio component.For example, the audio component can include at least one audio segment.A transport object identifier for the audio segment may have a specificvalue.

A description will be given of the FIC.

The FIC may include SSC bootstrapping information for acquiring servicelayer signaling data transmitted through an SSC. For example, the SSCbootstrapping information can include a source IP address (sIPAdres1), adestination IP address (IPAdrs1), a destination port number (Port1), atransport session identifier (tsi0-s), a transport object identifier(toi-s-bundl) and/or USD path information (usdUri), which are associatedwith the SSC.

A description will be given of the SSC.

The SSC C620200 may be identified by a transport session identifierhaving a value of “tsi-s” and/or a transport object identifier having avalue of “toi-s-bundl”. The SSC C620200 may include USD C620210, MPDC620230 and/or an SDP C620240.

A description will be given of the USD.

The USD C620210 may describe service layer properties. In addition, theUSD C620210 may include reference information (or URI) used to refer tothe MPD C620230 and/or the SDP C620240. For example, the USD(bundleDescription/userServiceDescription) C620210 may include anatscServiceDescription element, a deliveryMethod element and/or anappService element. The contents of the USD C620210 can include thecontents of the aforementioned USD. A description will be given of theUSD with reference to the attached drawing.

The atscServiceDescription element may include an atscSdpURI element.The atscSdpURI element may include information (URL information or URIinformation) used to refer to an SDP (or S-TSID) which provides accessrelated parameters for transport sessions through which service contentis transmitted. For example, the atscSdpURI element can have a value of“sdpUri” for referring to the SDP C620240.

The deliveryMethod element may include an atscAppService element. TheatscAppService element may include a basePattern element. ThebasePattern element may refer to segment URL information to which eachcomponent is mapped in the MPD.

The appService element may include an appServiceDescriptionURIattribute. The appServiceDescriptionURI attribute refers to information(URL information or URI information) used to refer to MPD includinginformation about all content components transmitted through a mobilebroadcast network (LTE broadcast), the Internet (unicast) and/or anormal broadcast network (ATSC broadcast or DVB broadcast). For example,the appServiceDescriptionURI attribute can have a value of “fullMpdUri”referring to the MPD C620230.

A description will be given of the MPD.

The MPD C620230 may include resource identifiers for individual mediacomponents of a linear/streaming service. The contents of the MPDaccording to the seventh embodiment of the present invention can includethe contents of the aforementioned MPD.

The MPD may include a Period element. The Period element may include afirst AdaptationSet element containing information about at least onevideo component and a second AdaptationSet element containinginformation about at least one audio component.

Each of the first AdaptationSet element and the second AdaptationSetelement may include a SegmentTemplate element and/or a Representationelement. The SegmentTemplate element may include default segmenttemplate information. The SegmentTemplate element may include a mediaattribute which contains template information for generating a mediasegment list. The Representation element may include information aboutrepresentation associated with a component. The Representation elementmay include an id attribute (or Rep_ID attribute) which specifiesrepresentation.

For example, a media attribute value for a video component can be“v-segUrl-$Num$.mp4”. An id attribute value for the video component canbe “RepresentationID-v”.

For example, a media attribute value for an audio component can be“ra-segUrl-$Num$.mp4”. An id attribute value for the audio component canbe “RepresentationID-ra”.

A description will be given of the SDP.

The SDP C620240 may include a first ROUTE session element which providesinformation about a ROUTE session for a service and/or a componentincluded in the service. The first ROUTE session element may includetransport path information for a first ROUTE session. For example, thefirst ROUTE session element can include a bsid attribute indicating theidentifier of a broadcast stream through which a content component ofthe service is transmitted, an sIdAddr attribute indicating the sourceIP address of the first ROUTE session, a dIpAddr attribute indicatingthe destination IP address of the first ROUTE session, a dport attributeindicating the destination port number of the first ROUTE session and/ora DP-ID attribute (or PLP_ID attribute) indicating the identifier of adata pipe (physical layer pipe) for the first ROUTE session. The bsidattribute, sIpAddr attribute, dIpAddr attribute, dport attribute and/orDP_ID attribute may be used as information on a transport path throughwhich LSID is transmitted. The SDP may be referred to as S-TSID. TheS-TSID is a kind of service layer signaling (SLS) XML fragment whichprovides all session description information for at least one transportsession through which at least one content component of the service istransmitted.

Specifically, the SDP C620240 may include component information (s), anoriginator and session identifier (o), connection information (c), mediadescription (m), an ATSC mode (a, atsc-mode) and/or TSI information (a,route-tsi). The contents of the SDP according to the seventh embodimentof the present invention can include the contents of the aforementionedSDP.

For example, the component information (s) can have a value of“robust-audio”. The originator and session identifier (o) can have avalue of “jdoe 2890844526 2890842807 IN IP4 sIPAdrs1”. The connectioninformation (c) can have a value of “c=IN IP4 IPAdrs1”. The mediadescription (m) can have a value of “APPLICATION port1 ROUTE/UDP 0”. TheATSC mode (a, atsc-mode) can have a value of “a=atsc-mode:BCStreamID1,BBPSID1”. The TSI information (a, route-tsi) can have avalue of “route-tsi: tsi-0”.

A description will be given of the LSID.

The LSID C620300 may include information about an LCT session includedin a ROUTE session. The LSID may include information identifying atransport session through which a component for a service istransmitted. The LSID may be included in each ROUTE session. The LSIDmay be transmitted through a specific transport session in thecorresponding ROUTE session. For example, the LSID C620300 can beidentified by a transport session identifier having a value of “tsi-0”,a transport object identifier having a value of “toi-0” and/or URIinformation having a value of “lsidUri”.

The LSID C620300 may include an SSC transport session element containinginformation about a transport session through which an SSC istransmitted, a first transport session element containing informationabout a transport session through which a video component is transmittedand/or a second transport session element containing information about atransport session through which an audio component is transmitted.

Each of the SSC transport session element, the first transport sessionelement and the second transport session element may include a tsiattribute which specifies a transport session through which a contentcomponent for a service is transmitted and/or a DP_ID attribute (orPLP_ID attribute) which indicates the identifier of a data pipe (orphysical layer pipe) associated with the transport session through whichthe content component for the service is transmitted.

In addition, each of the SSC transport session element, the firsttransport session element and the second transport session element mayinclude a SourceFlow element which provides information about a sourceflow included in the corresponding transport session.

The SourceFlow element may include an extended file delivery table(EFDT) element. The EFDT element may include the contents of filedelivery data in the form of an extended FDT instance including nominalFDT instance parameters. The EFDT element may include a FileTemplateelement. The FileTemplate element may indicate a file URL. The file URLhas the same value as the Content-Location attribute of an FDT. Inaddition, the FileTemplate element may indicate a template format forderivation of the file URI.

The SourceFlow element may include an ApplicationIdentifier elementand/or a PayloadFormat element.

The ApplicationIdentifier element may be referred to as a ContentInfoelement. The ContentInfo element may include additional informationmapped to the service (or application service) transmitted through thecorresponding transport session. For example, the ContentInfo elementcan include a representation ID of DASH content and/or adaptation setparameters of DASH media representation in order to select an LCTtransport session for rendering. The representation ID is an identifierassociated with a component for the service and may be referred to as aRep_ID attribute.

The PayloadFormat element may be referred to as a Payload element. ThePayload element may include information about a payload of a ROUTEpacket (or LCT packet) carrying objects of the source flow. The Payloadelement may include a CP attribute. The CP attribute may be referred toas a codePoint attribute. The codePoint attribute is a numericalrepresentation of a combination of values specified for the childelements and attributes of the Payload element. That is, the codePointattribute can indicate the type of payload transmitted by thecorresponding packet. In addition, the CP attribute may be referred toas a formatID attribute. The format ID attribute may specify a payloadformat of a delivery object. For example, the formatID attribute canindicate one of File Mode, Entity Mode and Package.

For example, the tsi attribute and the DP_ID attribute included in thefirst transport session element can respectively have a value of “tsi-v”and a value of “BBPSID2”. The FileTemplate element included in the firsttransport session element can have a value ofhttp://bc/v-segUrl-$TOI$.mp4, the Rep_ID attribute can have a value of“RepresentationID-v” and the CP attribute can indicate “EntityMode”.

In addition, the tsi attribute and the DP_ID attribute included in thesecond transport session element can respectively have a value of“tsi-ra” and a value of “BBPSID1”. The FileTemplate element included inthe second transport session element can have a value ofhttp://bc/ra-segUrl-$TOI$.mp4, the Rep_ID attribute can have a value of“RepresentationID-ra” and the CP attribute can indicate “EntityMode”.

The tsi attribute included in the SSC transport session element can havea value of “tsi-s” and the DP_ID attribute can have a value of“BBPSID1”. The EFDT element may include a File element. The File elementmay include a Content_Location attribute and a TOI attribute. TheContent_Location attribute may indicate a URL associated with an objecthaving a specific TOI value in the corresponding transport session. Forexample, the Content_Location attribute can have a value of “usdUri”.The TOI attribute may identify an object transmitted through thetransport session. For example, the TOI attribute can have a value of“toi-s-bundl”. The CP attribute included in a third transport sessionelement may indicate “FileMode(Meta)”.

A broadcast reception apparatus according to the seventh embodiment ofthe present invention can acquire a service on the basis of signalingdata. Specifically, the broadcast reception apparatus can acquire lowlevel signaling data and obtain service layer signaling data on thebasis of the low level signaling data. Then, the broadcast receptionapparatus can determine properties of a service using service layersignaling data (USD). Subsequently, the broadcast reception apparatuscan select at least one component for the service using service layersignaling data (MPD). For example, the broadcast reception apparatus canselect at least one component for the service using at least onerepresentation ID of the MPD. Then, the broadcast reception apparatuscan acquire information on a transport path through which the selectedat least one component is transmitted using service layer signaling data(SDP and/or LSID). Subsequently, the broadcast reception apparatus canacquire service data for the service on the basis of the information onthe transport path.

FIG. 63 illustrates a method for reducing a signaling size according toan eighth embodiment of the present invention.

When a corresponding session is transmitted using ROUTE/DASHtransmission and the session description protocol in a hybrid broadcastnetwork, the eighth embodiment of the present invention can reduceredundancy and configure minimum necessary signaling information usingthe relationship shown in FIG. 63.

Session time information may be optionally included in LSID. The sessiontime information may be mandatorily included in the SDP. Accordingly,the session time information can be included in the SDP using “t=” valueof the SDP.

IP/Port information is not included in the LSID. Since the SDP describesan IP/Port value at a session level, an ATSC SDP is defined such thatthe ATSC SDP describes the IP/Port information related to transmissionof a ROUTE session for ATSC signaling.

As to TSI information, the LSID describes TSI information of alltransport sessions constituting a ROUTE session. The SDP describestransport information or TSI information about one ROUTE session. When acomponent is transmitted through ATSC broadcast, information about adata pipe (or physical layer pipe) to which a transport session throughwhich the component is transmitted belongs is needed. In this case, aDP_ID (or PLP_ID) may be added to the SDP and/or the LSID by beingmapped thereto on the basis of the TSI information described in the LSIDand/or the SDP. When the DP_ID is added to the SDP, the DP_ID needs tobe described per TSI.

FEC information may be included in the LSID. Although the FECinformation is described in the SDP, the FEC information is described inRepair Flow of the LSID when the ROUTE/DASH transmission scheme is usedand thus the value of the FEC information can be used.

Language information is described in the SDP. However, when theROUTE/DASH transmission scheme is used, the language information isdescribed in MPD. Accordingly, the language information is not definedin the SDP and values of MPD can be used.

Data rate information is described in the SDP. However, when theROUTE/DASH transmission scheme is used, the data rate information isdescribed in MPD. Accordingly, the data rate information is not definedin the SDP and values of MPD can be used.

FIG. 64 illustrates USD according to a ninth embodiment of the presentinvention.

The ninth embodiment of the present invention can provide a method fordescribing additional attributes for reference information of sessiondescription of the USD (or SMT) and a method for including additionaldescription information in the USD.

Referring to FIG. 64(a), the USD (or SMT) may include a protocolVersionattribute, an atscServiceId attribute, a globalServiceId attribute, afullMpdURI attribute, an atscSdpURI element, a CapabilityDescriptionelement, a TargetingDescription element, a ContentAdvisoryDescriptionelement, a ProgramTitleDescription element, a ContentLabelDescriptionelement and/or an OriginalServiceIdDescription element.

The protocolVersion attribute may indicate the protocol version of anSSC (service signaling channel or service layer signaling data). Forexample, the protocolVersion attribute can include amajor_protocol_version attribute which indicates the major versionnumber of a protocol used to transmit an SSC (service signaling channel,S-TSID and/or service layer signaling data) for a service and/or aminor_protocol_version attribute which indicates the minor versionnumber of the protocol.

The atscServiceId attribute is a unique identifier for identifying aservice. The atscServiceId attribute may refer to a service entrycorresponding to low level signaling data (LLS, FIC or SLT). TheatscServiceId attribute may have the same value as a service identifier(serviceID) allocated to the service entry corresponding to the lowlevel signaling data (LLS, FIC or SLT).

The globalServiceId attribute is a globally unique identifier used forservice mapping between 3GPP USD and an ESG. The globalServiceIdattribute may have the same value as the service identifier (service_id)of the 3GPP USD and the service identifier (service_id) of the ESG. TheglobalServiceId attribute is a globally unique uniform resourceidentifier (URI) for identifying a service. The globalServiceIdattribute is a unique value within the range of broadcast streamidentifiers (BSID). In addition, the globalServiceId attribute may beused to access ESG data.

The fullMpdURI attribute indicates information (URL information or URIinformation) referring to MPD including information about all contentcomponents of a service transmitted through at least one of a mobilebroadcast network (LTE broadcast), the Internet (unicast) and a normalbroadcast network (ATSC broadcast or DVB broadcast).

The atscSdpURI element refers to information (URL information or URIinformation) indicating an SDP including information about a ROUTEsession through which a service (ATSC service or DVB service) istransmitted. The atscSdpURI element represents information (URLinformation or URI information) referring to an S-TSID (or ATSC_SDP)which provides access related parameters with respect to transportsessions through which service content is delivered. The atscSdpURIelement may include an essentialSdp attribute. Since an ATSC service canbe composed of two or more ROUTE sessions, two or more SDPs describing asingle ROUTE session can be referred to. In this case, since a receivercannot be aware of an SDP and a ROUTE session that need to be receivedfirst, the ninth embodiment of the present invention provides theessentialSdp attribute such that the receiver preferentially receives anSDP corresponding to an essentialSdp attribute value of “true” andpreferentially acquires a ROUTE session corresponding to the SDP. Whenthe value of the essentialSdp attribute is not described, theessentialSdp attribute is defined as a default value of “true”.

The CapabilityDescription element refers to a descriptor which describescapability that the receiver needs to have in order to provide services.The CapabilityDescription attribute may specify capabilities and/orcapability groups necessary for the receiver to achieve meaningfulreproduction of service content.

The TargetingDescription element may indicate a target device to which aservice will be provided.

The ContentAdvisoryDescription element may refer to information aboutcontent advisory related to a provided service. TheContentAdvisoryDescription element may specify content advisory ratingwith respect to the provided service.

The ProgramTitleDescription element may refer to information about thetitle of a service. The ProgramTitleDescription element may indicate thename of a service in a specific language.

The ProgramTitleDescription element may include acurrent_program_start_time attribute, a current_program_durationattribute and/or a title_text element.

The current_program_start_time attribute indicates a program start time.The current_program_start_time attribute may indicate a program starttime represented as NTP time.

The current_program_duration attribute may indicate a program durationfrom the program start time. The program duration may be represented inseconds.

The title_text element represents actual text which indicates the nameof a service. The title_text element may include a lang attribute. Thelang attribute may indicate the language of the service name. TheContentLabelDescription element may refer to a content label of aservice. The ContentLabelDescription element may indicate the name of acomponent.

The OriginalServiceIdDescription element refers to the original serviceof the corresponding service. The OriginalServiceIdDescription elementmay include an originalServiceId attribute. The originalServiceIdattribute may refer to an ID assigned to the original service of thecorresponding service.

FIG. 64(b) shows an example of the CapabilityDescription element.

The CapabilityDescription element is composed of a code and a stringwhich indicate capability, and a CapabilityDescription element value canbe represented as a string. A regular expression of the string may beconfigured in the same form as the format used in service announcement.

FIG. 65 illustrates service layer signaling according to the ninthembodiment of the present invention.

A broadcast signal C650100 having a specific frequency may includeservice data and/or signaling data for a service. For example, theservice can have an identifier of “SrvcID1”. The broadcast signalC650100 can be identified by “BCStreamID1”.

The service data may include base service data for a base service and/orenhanced service data for an enhanced service. The base service mayrefer to a service of a specific level. The enhanced service may referto a service of a higher level than the base service. For example, thebase service can be an HD service and the enhanced service can be a UHDservice. The base service can be a 2D service and the enhanced servicecan be a 3D service.

The base service data may include a base video component and/or a baseaudio component for the base service. The enhanced service data mayinclude an enhanced video component and/or an enhanced audio componentfor the enhanced service. Each of the base video component and theenhanced video component may include at least one video segmentincluding video data. Each of the base audio component and the enhancedaudio component may include at least one audio segment including audiodata.

The broadcast signal C650100 may include a base ROUTE session and/or anenhanced ROUTE session. The base service data may be transmitted throughthe base ROUTE session and the enhanced service data may be transmittedthrough the enhanced ROUTE session. Each of the base video component andthe base audio component may be transmitted through a specific transportsession (e.g. LCT session) in the base ROUTE session. Each of theenhanced video component and the enhanced audio component may betransmitted through a specific transport session (e.g. LCT session) inthe enhanced ROUTE session.

The signaling data may include low level signaling data and/or servicelayer signaling data. For example, the low level signaling data caninclude an FIC and/or an SLT. The low level signaling data may beincluded in an IP/UDP packet and transmitted. The service layersignaling data may be referred to as SLS. The service layer signalingdata may include USD, MPD (or full MPD), SDP (or ATSC SDP) and/or LSID.The USD, MPD and/or SDP may be transmitted through a service signalingchannel (SSC). An SSC and/or LSID may be transmitted through a specifictransport session of the base ROUTE session.

The base ROUTE session may be identified by a combination of a source IPaddress (sIPAdrs2), a destination IP address (IPAdrs2) and a destinationport number (Port2). In addition, the base ROUTE session may betransmitted through a first DP (BBPSID1) and/or a second DP (BBPSID2).Furthermore, the base ROUTE session may include a base SSC transportsession (tsi-s), a base LSID transport session (tsi-0), a base videotransport session (tsi-v) and/or a base audio transport session(tsi-ra).

The base SSC transport session (tsi-s) may include at least one SSCfragment. The at least one SSC fragment may be identified by a transportobject identifier. For example, the transport object identifier for theSSC fragment can have a value of “toi-s-bundl”. The USD, MPD and/or SDPmay be transmitted through the SSC transport session.

The base LSID transport session (tsi-0) may include at least one baseLSID fragment. For example, a transport object identifier for the baseLSID can have a value of “toi-0”. The base LSID may be transmittedthrough the base LSID transport session.

The base video transport session (tsi-v) may include a base videocomponent. For example, the base video component can include at leastone video segment. A transport object identifier for the video segmentmay have a specific value.

The base audio transport session (tsi-ra) may include a base audiocomponent. For example, the base audio component can include at leastone audio segment. A transport object identifier for the audio segmentmay have a specific value.

The enhanced ROUTE session may be identified by a combination of asource IP address (sIPAdrs1), a destination IP address (IPAdrs1) and adestination port number (Port1). In addition, the enhanced ROUTE sessionmay be transmitted through a first DP (BBPSID1) and/or a third DP(BBPSID3). Furthermore, the enhanced ROUTE session may include anenhanced LSID transport session (tsi-0), an enhanced video transportsession (tsi-ev) and/or an enhanced audio transport session (tsi-re).

The enhanced LSID transport session (tsi-0) may include at least oneenhanced LSID fragment. For example, a transport object identifier forthe enhanced LSID can have a value of “toi-0”. The enhanced LSID may betransmitted through the enhanced LSID transport session.

The enhanced video transport session (tsi-ev) may include an enhancedvideo component. For example, the enhanced video component can includeat least one video segment. A transport object identifier for the videosegment may have a specific value.

The enhanced audio transport session (tsi-ea) may include an enhancedaudio component. For example, the enhanced audio component can includeat least one audio segment. A transport object identifier for the audiosegment may have a specific value.

A description will be given of the FIC.

The FIC may include SSC bootstrapping information for acquiring servicelayer signaling data transmitted through an SSC. For example, the SSCbootstrapping information can include a source IP address (sIPAdres2), adestination IP address (IPAdrs2), a destination port number (Port2), atransport session identifier (tsi0-s), a transport object identifier(toi-s-bundl) and/or USD path information (usdUri), which are associatedwith the SSC.

A description will be given of the SSC.

The SSC C650200 may be identified by a transport session identifierhaving a value of “tsi-s” and/or a transport object identifier having avalue of “toi-s-bundl”. The SSC C650200 may include USD C650210, fullMPD C650230, an enhanced SDP C650240 and/or a base SDP C650250.

A description will be given of the USD.

The USD C650210 may describe service layer attributes. In addition, theUSD C650210 may include reference information (or URI) referring to thefull MPD C650230, the enhanced SDP C650240 and/or the base SDP C650250.For example, the USD (bundleDescription/userServiceDescription) C650210can include an atscServiceDescription element, a deliveryMethod elementand/or an appService element. The contents of the USD C650210 caninclude the contents of the aforementioned USD. A description will begiven of the USD with reference to the attached drawing.

The atscServiceDescription element may include an atscSdp1Uri elementfor the enhanced SDP and/or an atscSdp2Uri element for the base SDP. TheatscSdp1Uri element and/or the atscSdp2Uri element may includeinformation (URL information or URI information) referring to an SDP (orS-TSID) which provides access related parameters for transport sessionsthrough which service content is transmitted. For example, theatscSdp1Uri element can have a value of “sdp1Uri” for referring to theenhanced SDP C650240 and the atscSdp2Uri element can have a value of“sdp2Uri” for referring to the base SDP C650250.

In addition, each of the atscSdp1Uri element and the atscSdp2Uri elementmay include an essentialSdp attribute. For example, the essentialSdpattribute included in the atscSdp1Uri element can have a value of“false” and the essentialSdp attribute included in the atscSdp2Urielement can have a value of “true”. That is, a broadcast receptionapparatus can acquire the base SDP first on the basis of theessentialSdp attribute and preferentially receive components transmittedthrough the base ROUTE session.

The deliveryMethod element may include an atscAppService element. TheatscAppService element may include a first basePattern element for anenhanced video component, a second basePattern element for a base videocomponent, a third basePattern element for an enhanced audio componentand a fourth basePattern element for a base audio component. EachbasePattern element may refer to segment URL information to which eachcomponent is mapped in MPD. For example, the first basePattern elementcan have a value of “. . . bc/rep_id-ev”, the second basePattern elementcan have a value of “. . . bc/rep_id-v”, the third basePattern elementcan have a value of “. . . bc/rep_id-ea” and the fourth basePatternelement can have a value of “. . . bc/rep_id-a”.

The appService element may include an appServiceDescriptionURIattribute. The appServiceDescriptionURI attribute indicates information(URL information or URI information) referring to MPD includinginformation about all content components transmitted through a mobilebroadcast network (LTE broadcast), the Internet (unicast) and/or anormal broadcast network (ATSC broadcast or DVB broadcast). For example,the appServiceDescriptionURI attribute can have a value of “fullMpdUri”referring to the MPD C650230.

A description will be given of the full MPD.

The full MPD C650230 may include resource identifiers for individualmedia components of a linear/streaming service. The contents of the fullMPD according to the ninth embodiment of the present invention caninclude the contents of the aforementioned MPD and/or full MPOD.

The full MPD may include a Period element. The Period element mayinclude a first AdaptationSet element containing information about atleast one video component and a second AdaptationSet element containinginformation about at least one audio component.

The first AdaptationSet element may include a Representation element forthe enhanced video component and/or a Representation element for thebase video component. The second AdaptationSet element may include aRepresentation element for the enhanced audio component and/or aRepresentation element for the base audio component.

Each Representation element may include an id attribute (or Rep_IDattribute) identifying a representation, a SegmentTemplate elementincluding segment template information and/or a dependencyId attributeindicating at least one complementary representation on whichcorresponding representation depends in decoding and/or presentationprocesses. The SegmentTemplate element may include a media attributeincluding template information for generating a media segment list.

For example, an id attribute for the enhanced video component can have avalue of “RepresentationID-ev” and a media attribute for the enhancedvideo component can have a value of “ev-segUrl-$Num$.mp4”.

For example, an id attribute for the base video component can have avalue of “RepresentationID-v”, a dependencyId attribute for the basevideo component can have a value of “RepresentationID-ev” and a mediaattribute for the base video component can have a value of“v-segUrl-$Num$.mp4”.

For example, an id attribute for the enhanced audio component can have avalue of “RepresentationID-ea” and a media attribute for the enhancedaudio component can have a value of “ea-segUrl-$Num$.mp4”.

For example, an id attribute for the base audio component can have avalue of “RepresentationID-ra” and a media attribute for the base audiocomponent can have a value of “ra-segUrl-$Num$.mp4”.

A description will be given of the enhanced SDP (SDP1) C650240.

The enhanced SDP C650240 may include an enhanced ROUTE session elementwhich provides information about an enhanced ROUTE session for a serviceand/or a component included in the service. The enhanced ROUTE sessionelement may include transport path information for the enhanced ROUTEsession.

Specifically, the enhanced SDP C650240 can include component information(s), an originator and session identifier (o), connection information(c), media description (m), an ATSC mode (a, atsc-mode) and/or TSIinformation (a, route-tsi). The contents of the enhanced SDP accordingto the ninth embodiment of the present invention can include thecontents of the aforementioned SDP.

For example, the component information (s) can have a value of“robust-audio”. The media description (m) can have a value of“APPLICATION (port1) ROUTE/UDP 0”. The connection information (c) canhave a value of “IN IP4 (IPAdrs1)”. The ATSC mode (a, atsc-mode) canhave a value of “atsc-mode: (BSStreamID1,BBPSID1)”. The TSI information(a, route-tsi) can have a value of “route-tsi: (tsi-0).

A description will be given of the base SDP (SDP2) C650250.

The base SDP C650250 may include a base ROUTE session element whichprovides information about a base ROUTE session for a service and/or acomponent included in the service. The base ROUTE session element mayinclude transport path information for the base ROUTE session.

Specifically, the base SDP C650250 can include component information(s), an originator and session identifier (o), connection information(c), media description (m), an ATSC mode (a, atsc-mode) and/or TSIinformation (a, route-tsi). The contents of the base SDP according tothe ninth embodiment of the present invention can include the contentsof the aforementioned SDP.

For example, the component information (s) can have a value of“robust-audio”. The media description (m) can have a value of“APPLICATION (port1) ROUTE/UDP 0”. The connection information (c) canhave a value of “IN IP4 (IPAdrs2)”. The ATSC mode (a, atsc-mode) canhave a value of “atsc-mode: (BSStreamID1,BBPSID1)”. The TSI information(a, route-tsi) can have a value of “route-tsi: (tsi-0).

A description will be given of the enhanced LSID (LSID1) C650300.

The enhanced LSID (LSID1) C650300 may include information about an LCTsession included in an enhanced ROUTE session. For example, the enhancedLSID C650300 can be identified by a transport session identifier havinga value of “tsi-0”, a transport object identifier having a value of“toi-0” and/or URI information having a value of “lsidUri”.

The enhanced LSID C650300 may include an enhanced video transportsession element containing information about a transport session throughwhich an enhanced video component is transmitted and/or an enhancedaudio transport session element containing information about a transportsession through which an enhanced audio component is transmitted.

Each of the enhanced video transport session element and the enhancedaudio transport session element may include a tsi attribute, a DP_IDattribute (or PLP_ID attribute) and/or a SourceFlow element. TheSourceFlow element may include an extended file delivery table (EFDT)element, an ApplicationIdentifier element and/or a PayloadFormatelement. The EFDT element may include a FileTemplate element. TheApplicationIdentifier element may be referred to as a ContentInfoelement. A representation identifier is related to a component for aservice and may be referred to as a Rep_ID attribute.

The PayloadFormat element may be referred to as a Payload element. ThePayload element may include a CP attribute. The CP attribute may bereferred to as a codePoint attribute and/or a formatID attribute.

For example, the tsi element included in the enhanced video transportsession element can have a value of “tsi-ev”, the FileTemplate elementcan have a value of http://bc/ev-segUrl-$TOI$.mp4, the Rep_ID attributecan have a value of “RepresentationID-ev” and the CP attribute canindicate “EntityMode”.

The tsi element included in the enhanced audio transport session elementcan have a value of “tsi-ea”, the FileTemplate element can have a valueof http://bc/ea-segUrl-$TOI$.mp4, the Rep_ID attribute can have a valueof “RepresentationID-ea” and the CP attribute can indicate “EntityMode”.

A description will be given of the base LSID (LSID2) C650400.

The base LSID (LSID2) C650400 may include information about an LCTsession included in a base ROUTE session. For example, the base LSIDC650400 can be identified by a transport session identifier having avalue of “tsi-0”, a transport object identifier having a value of“toi-0” and/or URI information having a value of “lsidUri”.

The base LSID C650400 may include an SSC transport session elementcontaining information about a transport session through which an SSC istransmitted, a base video transport session element containinginformation about a transport session through which a base videocomponent is transmitted and/or a base audio transport session elementcontaining information about a transport session through which a baseaudio component is transmitted.

Each of the SSC transport session element, the base video transportsession element and the base audio transport session element may includea tsi attribute, a DP_ID attribute (or PLP_ID attribute) and/or aSourceFlow element. The SourceFlow element may include an EFDT element,an ApplicationIdentifier element and/or a PayloadFormat element. TheEFDT element may include a FileTemplate element. TheApplicationIdentifier element may be referred to as a ContentInfoelement. A representation identifier is related to a component for aservice and may be referred to as a Rep_ID attribute. The PayloadFormatelement may be referred to as a Payload element. The Payload element mayinclude a CP attribute. The CP attribute may be referred to as acodePoint attribute and/or a formatID attribute.

For example, the tsi element included in the base video transportsession element can have a value of “tsi-v”, the FileTemplate elementcan have a value of http://bc/v-segUrl-$TOI$.mp4, the Rep_ID attributecan have a value of “RepresentationID-v” and the CP attribute canindicate “EntityMode”.

The tsi element included in the base audio transport session element canhave a value of “tsi-ra”, the FileTemplate element can have a value ofhttp://bc/ra-segUrl-$TOI$.mp4, the Rep_ID attribute can have a value of“RepresentationID-ra” and the CP attribute can indicate “EntityMode”.

In addition, the tsi element included in the SSC transport sessionelement can have a value of “tsi-s”. The EFDT element may include a Fileelement. The File element may include a Content_Location attribute and aTOI attribute. For example, the Content_Location attribute can have avalue of “usdUri”. The TOI attribute can have a value of “toi-s-bundl”.In addition, the CP attribute included in the SSC transport sessionelement can indicate “FileMode(Meta)”.

A broadcast reception apparatus according to the ninth embodiment of thepresent invention can acquire a service on the basis of signaling data.Specifically, the broadcast reception apparatus can acquire low levelsignaling data and obtain service layer signaling data on the basis ofthe low level signaling data. Then, the broadcast reception apparatuscan determine properties of a service using service layer signaling data(USD). Subsequently, the broadcast reception apparatus can select atleast one component for the service using service layer signaling data(MPD). For example, the broadcast reception apparatus can select atleast one component for the service using at least one representation ID(or id attribute) of the MPD. Then, the broadcast reception apparatuscan acquire information on a transport path through which the selectedat least one component is transmitted using service layer signaling data(SDP and/or LSID). Subsequently, the broadcast reception apparatus canacquire service data for the service on the basis of the information onthe transport path.

The broadcast reception apparatus according to the ninth embodiment ofthe present invention can determine an SDP, which should bepreferentially acquired, through the essentialSDP attribute of theatscSdpURI and receive a component transmitted through a ROUTE sessioncorresponding to the SDP. The broadcast reception apparatus according tothe ninth embodiment of the present invention can perform fast channelchange since the broadcast reception apparatus can preferentiallyreceive information (LCT session through which A/V components aretransmitted) which is essential for A/V rendering in case of channelchange. In addition, the ninth embodiment of the present invention canaffect memory buffer management of the broadcast reception apparatus oroperation of the broadcast reception apparatus according tocapabilities.

FIG. 66 illustrates a configuration of signaling data according to atenth embodiment of the present invention.

A simple service refers to a case in which service signaling, audio andvideo are transmitted in a single data pipe (or physical layer pipe) andservice signaling/LSID are transmitted through a single LCT session.Services other than the simple service are referred to as full services.

When service signaling is provided in a full service structure, an SSCcan include USD, an SDP, MPD, LSID and/or signaling data such asInitSegment. A broadcast reception apparatus can render at least one ofan audio component, a video component and a caption component on ascreen on the basis of the SSC. Service signaling data has the followingrelationship.

The signaling data according to the tenth embodiment of the presentinvention may include low level signaling data and/or service layersignaling data.

The low level signaling data may include an FIC and/or RRD. The FIC maybe referred to as a service list table (SLT). The FIC may include SSCbootstrapping information (or SLS bootstrapping information). Abroadcast reception apparatus may participate in a transport sessionthrough which the SSC is transmitted and acquire the SSC on the basis ofthe FIC. The contents of the low level signaling data according to thetenth embodiment of the present invention can include the contents ofthe aforementioned low level signaling data.

The contents of the service layer signaling data according to the tenthembodiment of the present invention can include the contents of theaforementioned service layer signaling data. The following descriptionis based on a difference between the service layer signaling dataaccording to the tenth embodiment of the present invention and theaforementioned service layer signaling data.

The service layer signaling data may include USD (or ATSC_USD), SDP (orATSC SDP), MPD, LSID and/or an initialization segment.

The USD may include a protocol_version attribute, a serviceID attribute,a globalServiceID attribute, a first atscSdpURI element, a secondatscSdpURI element and/or an MPDUri element.

Each of the first atscSdpURI element and the second atscSdpURI elementmay include a URL attribute containing information about a path throughwhich the ATSC SDP can be acquired and a version attribute containingversion information of the ATSC SDP. For example, the URL attributeincluded in the first atscURI element can include information about apath through which a first ATSC SDP C660210 can be acquired and the URLattribute included in the second atscURI element can include informationabout a path through which a second ATSC SDP C660230 can be acquired.

The MPDUri element may include a URL attribute containing informationabout a path through which the MPD can be acquired, a major_versionattribute containing major version information of the MPD and/or aminor_version attribute containing minor version information of the MPD.

The MPD may include information (URL) about a path through which theinitialization segment can be accessed. The initialization segment mayinclude initialization information for accessing representation. Forexample, the initialization segment can include a video initializationsegment IS-V for a video component, an audio initialization segment IS-Afor an audio component and/or a caption initialization segment IS-C fora caption component.

In addition, the MPD may include information (URL) about a path throughwhich a media segment can be accessed. The media segment may includeencoded media content components. For example, the media segment caninclude a media segment containing data of an encoded video componentand/or a media segment containing data of an encoded audio component.

The first ATSC SDP C660210 may include a first ROUTE session elementwhich provides information about a first ROUTE session C660310containing information about a service and/or a component included inthe service. The first ROUTE session element may include transport pathinformation for the first ROUTE session C660310. For example, thetransport path information for the first ROUTE session C660310 can beused as information on a path through which a first LSID C660410 istransmitted. The broadcast reception apparatus can participate in atransport session through which the first LSID C660410 is transmittedand acquire the first LSID C660410.

The second ATSC SDP C660230 may include a second ROUTE session elementwhich provides information about a second ROUTE session C660330containing information about a service and/or a component included inthe service. The second ROUTE session element may include transport pathinformation for the second ROUTE session C660330. For example, thetransport path information for the second ROUTE session C660330 can beused as information on a path through which a second LSID C660430 istransmitted. The broadcast reception apparatus can participate in atransport session through which the second LSID C660430 is transmittedand acquire the second LSID C660430.

The first LSID C660410 may include information about a transport session(LCT session) in which a video component is transmitted through thefirst ROUTE session C660310. The first LSID C660410 may be transmittedthrough a specific transport session in the first ROUTE session C660310.The broadcast reception apparatus can participate in a specifictransport session on the basis of the first LSID C660410 and acquire thevideo component.

The second LSID C660430 may include information about a transportsession (LCT session) in which an audio component is transmitted throughthe second ROUTE session C660330. The second LSID C660430 may betransmitted through a specific transport session in the second ROUTEsession C660330. The broadcast reception apparatus can participate in aspecific transport session on the basis of the second LSID C660430 andacquire the audio component.

A broadcast reception apparatus according to the tenth embodiment of thepresent invention can acquire a service on the basis of signaling data.Specifically, the broadcast reception apparatus can acquire low levelsignaling data and acquire service layer signaling data on the basis ofthe low level signaling data. Then, the broadcast reception apparatuscan determine properties of a service using service layer signaling data(USD). Subsequently, the broadcast reception apparatus can select atleast one component for the service using service layer signaling data(MPD). For example, the broadcast reception apparatus can select atleast one component for the service using at least one representation IDof the MPD. Then, the broadcast reception apparatus can acquireinformation on a transport path through which the selected at least onecomponent is transmitted using the service layer signaling data(initialization segment, SDP and/or LSID). Subsequently, the broadcastreception apparatus can acquire service data for the service on thebasis of the information on the transport path.

FIG. 67 illustrates a configuration of the signaling data according tothe tenth embodiment of the present invention.

When a service transmitted through ATSC broadcast is fully signaled, thetenth embodiment of the present invention can provide extended USD forreducing channel change time.

The USD according to the tenth embodiment of the present invention mayinclude a protocolVersion attribute, an atscServiceId attribute, aglobalServiceId attribute, an atscSdpUri element and/or a fullMpdUrielement.

The protocolVersion attribute may indicate the protocol version of anSSC (service signaling channel or service layer signaling data).

The atscServiceId attribute is an identifier which uniquely identifies aservice.

The globalServiceId attribute is a globally unique identifieridentifying a service.

The atscSdpUri element refers to information (URL information or URIinformation) indicating an ATSC SDP referred to in the USD. TheatscSdpUri element indicates information (URL information or URIinformation) referring to S-TSID (or ATSC_SDP) which provides accessrelated parameters for transport sessions through which service contentis transmitted. The atscSdpUri element may include a version attributeand/or a URL attribute. The version attribute may indicate the versioninformation of the ATSC SDP referred to by the atscSdpUri. The URLattribute may represent the URL indicating the unique URI of theatscSdpUri.

The fullMpdUri element may indicate the URL address of full MPD referredto in the USD. The fullMpdUri element is information (URL information orURI information) referring to MPD including information about allcontent components of a service transmitted through a mobile broadcastnetwork (LTE broadcast), the Internet (unicast) and/or a normalbroadcast network (ATSC broadcast or DVB broadcast). The fullMpdUrielement may include a URL attribute containing information about a paththrough which the MPD can be acquired, a major_version attributecontaining major version information of the MPD and/or a minor_versionattribute containing minor version information of the MPD. Whenconfiguration information of the MPD is changed and thus the broadcastreception apparatus cannot perform A/V rendering using previouslyreceived MPD and LCT header additional information, the value of themajor_version attribute can increase. If the broadcast receptionapparatus can perform audio rendering and/or video rendering usingpreviously received and cached MPD and LCT header additional information(e.g. EXT_PRESENTATION_TIME header), the major_version attribute valueis not changed and the minor_version attribute value can increase.

FIG. 68 illustrates an example of transmitting service layer signalingdata according to transmission intervals thereof according to the tenthembodiment of the present invention.

FIG. 68 shows service layer signaling data C681000 according to thetenth embodiment of the present invention. The service layer signalingdata C681000 may include USD, MPD, SDP, LSID and/or an initializationsegment.

According to the tenth embodiment of the present invention, transmissionintervals of service layer signaling data, USD, MPD, LSID and/or theinitialization segment, which are necessary to render, are shorter thanthat of the SDP which describes only transmission information of theLSID.

Accordingly, a broadcast reception apparatus according to the tenthembodiment of the present invention can reduce channel change time usingversion information and/or URI information of the USD.

A description will be given of a method for managing version informationof the SDP by the broadcast reception apparatus according to the tenthembodiment of the present invention.

The broadcast reception apparatus may receive and/or acquire the servicelayer signaling data C681000.

The broadcast reception apparatus may compare version information(version attribute value) of the SDP mapped to the corresponding uri(uri attribute value) with cached SDP version information upon receptionof the USD.

If the version information of the SDP mapped to the corresponding uridiffers from the cached SDP version information, the broadcast receptionapparatus may newly receive and/or cache the SDP.

If the version information of the SDP mapped to the corresponding uri isidentical to the cached SDP version information, the broadcast receptionapparatus may not receive and/or cache the SDP.

Accordingly, the broadcast reception apparatus may not compare theversion information in the header of Metadata_envelope or parse the SDP,and thus the broadcast reception apparatus can reduce channel changetime by checking whether the SDP has been changed on the basis of theUSD.

For example, the atscSDPURI element of USD C681110 can include pathinformation and/or version information related to an SDP C681510. Theversion attribute included in the atscSDPURI element can have a value of“1” and the uri attribute can have a value of “SDP_URL_1”.

In addition, the atscSDPURI element of USD C681130 can also include pathinformation and/or version information related to the SDP C681510. Theversion attribute included in the atscSDPURI element can have a value of“1” and the uri attribute can have a value of “SDP_URL_1”.

The atscSDPURI element of USD C681150 can include path informationand/or version information related to an SDP C681530. The versionattribute included in the atscSDPURI element can have a value of “2” andthe uri attribute can have a value of “SDP_URL_2”.

Here, it is assumed that the broadcast reception apparatus receivesand/or caches the SDP C681510.

The USD C681110 and the USD C681130 refer to the same SDP C681510. Thatis, the broadcast reception apparatus does not re-receive and/or cachethe SDP C681510 since the version information of the SDP C681510 mappedto the corresponding uri is identical to the version information of thecached SDP C681510 when the USD C681130 is received.

However, the USD C681130 and the USD C681150 respectively refer to SDPC681510 and SDP C681530. That is, the broadcast reception apparatus canreceive and/or cache the SDP C681530 since the version information ofthe SDP C681530 mapped to the corresponding uri differs from the versioninformation of the cached SDP C681510 when the USD C681150 is received.

A description will be given of a method for managing version informationof MPD by the broadcast reception apparatus according to the tenthembodiment of the present invention.

The broadcast reception apparatus may compare version information(version attribute value) of MPD mapped to the corresponding MPD uri(uri attribute value) with cached MPD version information upon receptionof the USD.

If the major version (major_version attribute value) of the MPD ischanged, the broadcast reception apparatus may receive, acquire and/orparse new MPD.

If the major version (major_version attribute value) of the MPD is notchanged and only the minor version (minor_version attribute value)thereof is changed, the broadcast reception apparatus can re-process theMPD using only the previously cached MPD and LCT header additionalattribute information.

If both the major version and the minor version are not changed, thebroadcast reception apparatus may not receive, acquire and/or parse theMPD.

Accordingly, the broadcast reception apparatus can reduce channel changetime by checking whether the MPD is changed on the basis of the USDwithout comparing versions in the header of Metadata_envelope or parsingthe MPD.

For example, the fullMPDURI element of the USD C681110 can include pathinformation and/or version information related to MPD C681210. Themajor_version attribute included in the fullMPDURI element can have avalue of “2”, the minor_version attribute can have a value of “1” andthe uri attribute can have a value of “MPD_URL_2”.

In addition, the fullMPDURI element of the USD C681130 can include pathinformation and/or version information related to MPD C681230. Themajor_version attribute included in the fullMPDURI element can have avalue of “2”, the minor_version attribute can have a value of “2” andthe uri attribute can have a value of “MPD_URL_3”.

The fullMPDURI element of the USD C681150 can include path informationand/or version information related to MPD C681250. The major_versionattribute included in the fullMPDURI element can have a value of “3”,the minor_version attribute can have a value of “2” and the uriattribute can have a value of “MPD_URL_4”.

Here, it is assumed that the broadcast reception apparatus receivesand/or caches the MPD C681210.

The major version (major_version attribute=2) of the MPD C681210referred to in the USD C681110 is identical to the major version(major_version attribute=2) of the MPD C681230 referred to in the USDC681130. However, minor version (minor_version attribute=1) of the MPDC681210 referred to in the USD C681110 differs from the minor version(minor_version attribute=2) of the MPD C681230 referred to in the USDC681130. Accordingly, the broadcast reception apparatus can re-process(or newly generate) MPD using only the previously cached MPD C681210and/or LCT header additional attribute information when the USD C681130is received. For example, the re-processed MPD can be identical to theMPD C681230. Then, the broadcast reception apparatus may cache there-processed MPD.

The major version (major_version attribute=2) of the MPD C681230referred to in the USD C681130 differs from the major version(major_version attribute=3) of the MPD C681250 referred to in the USDC681150. Accordingly, the broadcast reception apparatus can receive,acquire and/or parse the new MPD C681250 when the USD C681150 isreceived.

FIG. 69 illustrates an example of transmitting service layer signalingdata according to transmission intervals thereof according to the tenthembodiment of the present invention.

FIG. 68 shows service layer signaling data C691000 according to thetenth embodiment of the present invention. The service layer signalingdata C691000 may include USD, MPD, SDP, LSID and/or an initializationsegment.

According to the tenth embodiment of the present invention, transmissionintervals of service layer signaling data, USD, MPD, LSID and/or theinitialization segment, which are necessary to render, are shorter thanthe SDP which describes only transmission information of the LSID.

Accordingly, the broadcast reception apparatus according to the tenthembodiment of the present invention can reduce channel change time usingversion information of the USD.

It is assumed that the broadcast reception apparatus according to thetenth embodiment of the present invention does not cache the servicelayer signaling data before first time C692100. Accordingly, thebroadcast reception apparatus may have no SDP and MPD cached therein.Otherwise, all SDPs and MPDs cached in the broadcast reception apparatusmay have a default value (0 or null). For example, version informationof an SDP can be “0” and URI information thereof can be “null”. Majorversion information of MPD can be “0”, minor version information thereofcan be “0” and URI information thereof can be “null”.

The broadcast reception apparatus according to the tenth embodiment ofthe present invention may join in the corresponding channel at the firsttime C692100. For example, the broadcast reception apparatus canparticipate in a transport session in which the service layer signalingdata C691000 is transmitted on the basis of SSC bootstrappinginformation of low level signaling data.

The broadcast reception apparatus may acquire the USD C691110 from theservice layer signaling data.

Then, the broadcast reception apparatus may acquire the MPD C691210and/or the SDP C691510 on the basis of the USD C691110.

For example, the broadcast reception apparatus can compare versioninformation of the MPD C691210 mapped to the corresponding MPD uri (uriattribute value) with version information of MPD cached therein on thebasis of the USD C691110. The fullMPDURI element of the USD C691110 mayinclude the path information and/or version information related to theMPD C691210. The major_version attribute included in the fullMPDURIelement may have a value of “2”, the minor_version attribute may have avalue of “1” and the uri attribute may have a value of “MPD_URL_2”.Since the major version information (major_version attribute value) hasbeen changed when the broadcast reception apparatus joins the channel atthe first time C692100, the broadcast reception apparatus can receiveand/or cache the new MPD C691210.

For example, the broadcast reception apparatus can compare versioninformation (version attribute value) of the SDP C691510 mapped to thecorresponding uri (uri attribute value) with version information of anSDP cached therein on the basis of the USD C691110. The atscSDPURIelement of the USD C691110 may include the path information and/orversion information related to the SDP C691510. The version attributeincluded in the atscSDPURI element may have a value of “1” and the uriattribute may have a value of “SDP_URL_1”. Since the version informationof the SDP C691510 mapped to the corresponding uri differs from theversion information of the cached SDP when the broadcast receptionapparatus joins the channel at the first time C692100, the broadcastreception apparatus can receive and/or cache the new SDP C691510.

Subsequently, the broadcast reception apparatus may acquire aninitialization segment C691310 on the basis of the MPD C691210.

In addition, the broadcast reception apparatus may acquire LSID C691410on the basis of the SDP C691510.

Then, the broadcast reception apparatus may acquire service data (e.g. avideo component and an audio component) for the corresponding service onthe basis of the initialization segment C691310 and/or the LSID C691410.

The broadcast reception apparatus joining the channel at the first timeC692100 may receive and/or cache the MPD C691210, the initializationsegment C691310, the LSID C691410 and/or the SDP C691510 on the basis ofthe USD C691110. Consequently, the version information of the SDP cachedin the broadcast reception apparatus can be “1” and the URI informationthereof can be “SDP_URL_1”. In addition, the major version informationof the MPD cached in the broadcast reception apparatus can be “2”, theminor version information thereof can be “1” and the URI informationthereof can be “MPD_URL_2”.

The broadcast reception apparatus according to the tenth embodiment ofthe present invention may rejoin the corresponding channel at secondtime C692200. For example, the broadcast reception apparatus canparticipate in a transport session in which the service layer signalingdata C691000 is transmitted on the basis of the SSC bootstrappinginformation of the low level signaling data.

The broadcast reception apparatus may acquire the USD C691150 from theservice layer signaling data.

Then, the broadcast reception apparatus may acquire the MPD C691250and/or the SDP C691550 on the basis of the USD C691150.

For example, the broadcast reception apparatus can compare versioninformation of the MPD C691250 mapped to the corresponding MPD uri (uriattribute value) with version information of MPD cached therein on thebasis of the USD C691150. The fullMPDURI element of the USD C691150 mayinclude the path information and/or version information related to theMPD C691250. The major version attribute included in the fullMPDURIelement may have a value of “2”, the minor version attribute may have avalue of “1” and the uri attribute may have a value of “MPD_URL_2”.Since both the major version information (major_version attribute value)and the minor version information (minor_version attribute) have notbeen changed when the broadcast reception apparatus joins the channel atthe second time C692200, the broadcast reception apparatus does notreceive and/or cache the new MPD C691250.

For example, the broadcast reception apparatus can compare versioninformation of the SDP C691550 mapped to the corresponding uri (uriattribute value) with version information of the SDP cached therein onthe basis of the USD C691150. The atscSDPURI element of the USD C691150may include the path information and/or version information related tothe SDP C691550. The version attribute included in the atscSDPURIelement may have a value of “2” and the uri attribute may have a valueof “SDP_URL_2”. Since the version information of the SDP C691550 mappedto the corresponding uri differs from the version information of thecached SDP when the broadcast reception apparatus joins the channel atthe second time C692200, the broadcast reception apparatus can receiveand/or cache the new SDP C691550.

Subsequently, the broadcast reception apparatus may acquire LSID C691450on the basis of the SDP C691550.

Then, the broadcast reception apparatus may acquire service data (e.g. avideo component and an audio component) for the corresponding service onthe basis of the LSID C691450.

The broadcast reception apparatus joining the channel at the second timeC692200 may receive and/or cache the LSID C691450 and/or the SDP C691550on the basis of the USD C691150. Consequently, the version informationof the SDP cached in the broadcast reception apparatus can be “2” andthe URI information thereof can be “SDP_URL_2”. In addition, the majorversion information of the MPD cached in the broadcast receptionapparatus can be “2”, the minor version information thereof can be “1”and the URI information thereof can be “MPD_URL_2”. That is, thebroadcast reception apparatus does not additionally receive the MPDC691250 and/or an initialization segment C691350 since versioninformation thereof is identical to the version information of thecached MPD and initialization segment.

Consequently, the broadcast reception apparatus can reduce channelchange time on the basis of version information.

FIG. 70 illustrates a configuration of signaling data according to athirteenth embodiment of the present invention.

Service layer signaling data for ATSC broadcast transmission accordingto the thirteenth embodiment of the present invention may include USD,SDP, MPD, LSID and/or an initialization segment (or InitSegment). Abroadcast reception apparatus can render an audio component, a videocomponent and/or a caption component on a screen on the basis of an SSC.The thirteenth embodiment of the present invention can provide a methodfor transmitting bootstrapping information of two or more ROUTE sessionswhich form a single service and/or service layer signaling data in amodified structure by extending the SDP.

The signaling data according to the thirteenth embodiment of the presentinvention may include low level signaling data and/or service layersignaling data.

The low level signaling data may include an FIC. The contents of the lowlevel signaling data according to the thirteenth embodiment of thepresent invention can include the contents of the aforementioned lowlevel signaling data.

The contents of the service layer signaling data according to thethirteenth embodiment of the present invention can include the contentsof the aforementioned service layer signaling data. The followingdescription is based on a difference between the service layer signalingdata according to the thirteenth embodiment of the present invention andthe aforementioned service layer signaling data.

The service layer signaling data may include USD (or ATSC_USD), SDP (orATSC SDP), MPD, LSID and/or an initialization segment.

The USD may include a protocol_version attribute, a serviceID attribute,a globalServiceID attribute, an atscSdpURI element and/or an MPDUrielement.

The atscSdpURI element may include a URL attribute containinginformation about a path through which the ATSC SDP can be acquired anda version attribute containing version information of the ATSC SDP. Forexample, the URL attribute included in the atscURI element can includeinformation about a path through which the ATSC SDP can be acquired.

The MPDUri element may include a URL attribute containing informationabout a path through which the MPD can be acquired, a major_versionattribute containing major version information of the MPD and/or aminor_version attribute containing minor version information of the MPD.

The MPD may include information (URL) about a path through which theinitialization segment can be accessed. The MPD may include information(URL) about a path through which a media segment can be accessed. Forexample, the media segment can include a media segment containing dataof an encoded video component and/or a media segment containing data ofan encoded audio component. The media data including the data of theencoded video component may be transmitted through a first ROUTE sessionC700310. The media data including the data of the encoded audiocomponent may be transmitted through a second ROUTE session C700330.

The ATSC SDP may include bootstrapping (LSID transport) information ofat least one ROUTE session constituting an ATSC service. Thebootstrapping information of the ROUTE session may be information foracquiring information about the ROUTE session. For example, theinformation about the ROUTE session can be LSID. The bootstrappinginformation of the ROUTE session may be information for acquiring LSID.The ATSC SDP may include a first ROUTE session element and/or a secondROUTE session element.

The first ROUTE session element may include information about the firstROUTE session C700310 containing information about a service and/or acomponent included in the service. The first ROUTE session element mayinclude transport path information for the first ROUTE session C700310.For example, the transport path information for the first ROUTE sessionC700310 can be used as information on a path through which a first LSIDC700311 is transmitted. The broadcast reception apparatus canparticipate in a transport session through which the first LSID C700311is transmitted and acquire the first LSID C700311.

The second ROUTE session element may include information about thesecond ROUTE session C700330 containing information about a serviceand/or a component included in the service. The second ROUTE sessionelement may include transport path information for the second ROUTEsession C700330. For example, the transport path information for thesecond ROUTE session C700330 can be used as information on a paththrough which a second LSID C700331 is transmitted. The broadcastreception apparatus can participate in a transport session through whichthe second LSID C700331 is transmitted and acquire the second LSIDC700331.

The first LSID C700311 may include information about at least onetransport session (LCT session), which is transmitted through the firstROUTE session C700310. The first LSID C700311 may be transmitted througha specific transport session in the first ROUTE session C700310. Thebroadcast reception apparatus can participate in a specific transportsession on the basis of the first LSID C700311 and acquire a component.

The second LSID C700331 may include information about at least onetransport session (LCT session), which is transmitted through the secondROUTE session C700330. The second LSID C700331 may be transmittedthrough a specific transport session in the second ROUTE sessionC700330. The broadcast reception apparatus can participate in a specifictransport session on the basis of the second LSID C700331 and acquire acomponent.

The broadcast reception apparatus according to the tenth embodiment ofthe present invention can acquire a service on the basis of signalingdata. Specifically, the broadcast reception apparatus can acquire lowlevel signaling data and acquire service layer signaling data on thebasis of the low level signaling data. Then, the broadcast receptionapparatus can determine properties of a service using service layersignaling data (USD). Subsequently, the broadcast reception apparatuscan select at least one component for the service using service layersignaling data (MPD). For example, the broadcast reception apparatus canselect at least one component for the service using at least onerepresentation ID of the MPD. Then, the broadcast reception apparatuscan acquire information on a transport path through which the selectedat least one component is transmitted using service layer signaling data(initialization segment, SDP and/or LSID). Subsequently, the broadcastreception apparatus can acquire service data for the service on thebasis of the information on the transport path.

FIG. 71 illustrates an SDP according to the thirteenth embodiment of thepresent invention.

Referring to FIG. 71(a), an ATSC SDP C710200 may include bootstrapping(LSID transport) information of at least one ROUTE session constitutingan ATSC service. The ATSC SDP C710200 may include a first ROUTE sessionelement C710210 and/or a second ROUTE session element C710220.

For example, the ROUTE session element can include a bsid attributewhich indicates the identifier of a broadcast stream in which a contentcomponent of a service is transmitted, an sIpAddr attribute whichindicates the source IP address of a corresponding ROUTE session, andIpAddr attribute which indicates the destination IP address of theROUTE session, a dport attribute which indicates the destination portnumber of the ROUTE session and/or a PLPID attribute which indicates aphysical layer parameter for the ROUTE session.

Referring to FIG. 71(b), the ROUTE session element may include mediadescription (m), connection information (c), a source filter (a,source-filter) and/or an ATSC mode (a, atsc-mode) according to anotherembodiment.

The media description (m) may indicate the name of media and/or thedescription port of the corresponding ROUTE session. For example, themedia description (m) can be represented as “application (Port)ROUTE/UDP 0”.

The connection information (c) may indicate the destination IP addressof the ROUTE session. For example, the connection information (c) can berepresented as “IN (version) (destinationIPaddress)”.

The source filter (a, source-filter) may indicate a source IP address.For example, the source filter (a) can be represented as “source-filter:incl IN (version) (sourceIPaddress)”.

The ATSC mode (a, atsc-mode) may indicate the ID of a transport streamin which LSID of the ROUTE session is transmitted and/or the ID of adata pipe (or PLP) through which the LSID of the ROUTE session istransmitted when the ATSC broadcast mode is used. For example, the ATSCmode (a, atsc-mode) can be represented as “atsc-mode:(broadcastStreamID, dataPipeID)”.

Referring back to FIG. 71(a), the first ROUTE session element C710210may include information about a first ROUTE session C710310. The firstROUTE session element C710210 may include transport path information forthe first ROUTE session C710310. For example, the transport pathinformation for the first ROUTE session C710310 can be used asinformation on a path through which first LSID C710311 is transmitted.The broadcast reception apparatus can participate in a transport sessionin which the first LSID C710311 is transmitted on the basis of thetransport path information and acquire the first LSID C710311.

For example, the media description (m) included in the first ROUTEsession element C710210 can have a value of “application destUDPPort1ROUTE/UDP 0”, the connection information (c) included therein can have avalue of “IN IP4 destIPAddr1”, the source filter (a) included thereincan have a value of “source-filter: incl IN IP4 sourceIPAddr1” and theATSC mode (a, atsc-mode) included therein can have a value of“atsc-mode: (BCStreamID1, DP_ID1)”.

The second ROUTE session element C710220 may include information about asecond ROUTE session C710330. The second ROUTE session element C710220may include transport path information for the second ROUTE sessionC710330. For example, the transport path information for the secondROUTE session C710330 can be used as information on a path through whichsecond LSID C710331 is transmitted. The broadcast reception apparatuscan participate in a transport session in which the second LSID C710331is transmitted on the basis of the transport path information andacquire the second LSID C710331.

For example, the media description (m) included in the second ROUTEsession element C710220 can have a value of “application destUDPPort2ROUTE/UDP 0”, the connection information (c) included in the secondROUTE session element C710220 can have a value of “IN IP4 destIPAddr2”,the source filter (a) included in the second ROUTE session elementC710220 can have a value of “source-filter: incl IN IP4 sourceIPAddr2”and the ATSC mode (a, atsc-mode) included in the second ROUTE sessionelement C710220 can have a value of “atsc-mode: (BCStreamID1, DP_ID2)”.

FIG. 72 illustrates service layer signaling according to the thirteenthembodiment of the present invention.

A broadcast signal C720100 having a specific frequency may includeservice data and/or signaling data for a service. For example, theservice can have an identifier of “SrvcID1”. The broadcast signalC720100 can be identified by “BCStreamID1”.

The service data may include base service data for a base service and/orenhanced service data for an enhanced service.

The broadcast signal C720100 may include a base ROUTE session and/or anenhanced ROUTE session. The base service data may be transmitted throughthe base ROUTE session and the enhanced service data may be transmittedthrough the enhanced ROUTE session.

The signaling data may include low level signaling data and/or servicelayer signaling data. For example, the low level signaling data caninclude an FIC. The service layer signaling data may include USD, MPD(or full MPD), SDP (or ATSC SDP) and/or LSID.

The base ROUTE session may be identified by a combination of a source IPaddress (sIPAdrs2), a destination IP address (IPAdrs2) and a destinationport number (Port2). In addition, the base ROUTE session may betransmitted through a first DP (DP_ID2). Furthermore, the base ROUTEsession may include a base SSC transport session (tsi-s), a base LSIDtransport session (tsi-0), a base video transport session (tsi-v) and/ora base audio transport session (tsi-ra).

The enhanced ROUTE session may be identified by a combination of asource IP address (sIPAdrs1), a destination IP address (IPAdrs1) and adestination port number (Port1). In addition, the enhanced ROUTE sessionmay be transmitted through a first DP (DP_ID1). Furthermore, theenhanced ROUTE session may include an enhanced LSID transport session(tsi-0), an enhanced video transport session (tsi-ev) and/or an enhancedaudio transport session (tsi-re).

The contents of the broadcast signal C720100 can include the contents ofthe aforementioned broadcast signal. The following description is basedon a difference between the broadcast signal C720100 and theaforementioned broadcast signal.

A description will be given of the FIC.

The FIC may include SSC bootstrapping information for acquiring servicelayer signaling data transmitted through an SSC.

A description will be given of the SSC.

The SSC C720200 may be identified by a transport session identifierhaving a value of “tsi-s” and/or a transport object identifier having avalue of “toi-s-bundl”. The SSC C720200 may include USD C720210, MPDC720230 and/or an SDP C720240.

A description will be given of the USD(bundleDescription/userServiceDescription).

The USD C720210 may describe service layer attributes. In addition, theUSD C720210 may include reference information (or URI) referring to theMPD C720230 and/or the SDP C720240. For example, the USD C720210 caninclude an atscServiceID attribute, fullMpdUri attribute and/or adeliveryMethod element.

The atscServiceId attribute is an identifier uniquely identifying aservice. For example, the atscServiceId attribute can have a value of“SrvID1”.

The fullMpdUri attribute represents information (URL information or URIinformation) referring to MPD, including information about all contentcomponents of a service, transmitted through a mobile broadcast network(LTE broadcast), the Internet (unicast) and/or a normal broadcastnetwork (ATSC broadcast or DVB broadcast). For example, the fullMpdUriattribute can have a value of “mpdUri”.

The deliveryMethod element may include an atscSdpURI element, a firstatscBroadcastAppService element and/or a second atscBroadcastAppServiceelement.

The atscSdpURI element may include information (URL information or URIinformation) referring to an SDP (or S-TSID) which provides accessrelated parameters for transport sessions delivering service content.For example, the atscSdpURI element can have a value of “sdpUri”referring to the SDP C720240.

The first atscBroadcastAppService element may include a DP_ID attributewhich identifies a data pipe through which component data for a serviceis transmitted, a first basePattern element for a base video componentand/or a second basePattern element for a base audio component. Forexample, the DP_ID attribute can have a value of “DP_ID2”, the firstbasePattern element can have a value of “. . . bc/(RepresentationID-v)”and the second basePattern element can have a value of “. . .bc/(RepresentationID-a)”.

The second atscBroadcastAppService element may include a DP_ID attributewhich identifies a data pipe through which component data for a serviceis transmitted, a third basePattern element for an enhanced videocomponent and/or a fourth basePattern element for an enhanced audiocomponent. For example, the DP_ID attribute can have a value of“DP_ID1”, the third basePattern element can have a value of “. . .bc/(RepresentationID-ev)” and the fourth basePattern element can have avalue of “. . . bc/(RepresentationID-ea)”.

A description will be given of the MPD.

The MPD C720230 may include a Period element. The Period element mayinclude a first AdaptationSet element containing information about atleast one video component and a second AdaptationSet element containinginformation about at least one audio component.

The first AdaptationSet element may include a Representation element forthe enhanced video component and/or a Representation element for thebase video component. The second AdaptationSet element may include aRepresentation element for the enhanced audio component and/or aRepresentation element for the base audio component.

Each Representation element may include an id attribute (or Rep_IDattribute) identifying a representation, a SegmentTemplate elementincluding segment template information and/or a dependencyId attributeindicating at least one complementary representation on whichcorresponding representation depends in decoding and/or presentationprocesses. The SegmentTemplate element may include a media attributeincluding template information for generating a media segment list.

For example, an id attribute for the enhanced video component can have avalue of “RepresentationID-ev”, a dependencyId attribute for theenhanced video component can have a value of “RepresentationID-v” and amedia attribute for the enhanced video component can have a value of“ev-segUrl-$Num$.mp4”.

For example, an id attribute for the base video component can have avalue of “RepresentationID-v” and a media attribute for the base videocomponent can have a value of “v-segUrl-$Num$.mp4”.

For example, an id attribute for the enhanced audio component can have avalue of “RepresentationID-ea” and a media attribute for the enhancedaudio component can have a value of “ea-segUrl-$Num$.mp4”.

For example, an id attribute for the base audio component can have avalue of “RepresentationID-ra” and a media attribute for the base audiocomponent can have a value of “ra-segUrl-$Num$.mp4”.

A description will be given of the SDP C720240.

The SDP 720240 may include an enhanced ROUTE session element whichprovides information about an enhanced ROUTE session and/or a base ROUTEsession element which provides information about a base ROUTE session.

The enhanced ROUTE session element and/or the base ROUTE session elementmay include media description (m), connection information (c), a sourcefilter (a, source-filter) and/or an ATSC mode (a, atsc-mode).

For example, media description (m) for the enhanced ROUTE session canhave a value of “application destUDPPort1 ROUTE/UDP 0”, the connectioninformation (c) for the enhanced ROUTE session can have a value of “INIP4 destIPAddr1”, the source filter (a) for the enhanced ROUTE sessioncan have a value of “source-filter: incl IN IP4 sourceIPAddr1” and theATSC mode (a, atsc-mode) for the enhanced ROUTE session can have a valueof “atsc-mode: (DP_ID1)”.

For example, media description (m) for the base ROUTE session can have avalue of “application destUDPPort2 ROUTE/UDP 0”, the connectioninformation (c) for the base ROUTE session can have a value of “IN IP4destIPAddr2”, the source filter (a) for the base ROUTE session can havea value of “source-filter: incl IN IP4 sourceIPAddr2” and the ATSC mode(a, atsc-mode) for the base ROUTE session can have a value of“atsc-mode: (DP_ID2)”.

A description will be given of the enhanced LSID 720300.

For example, a tsi attribute included in an enhanced video transportsession element can have a value of “tsi-ev”, a FileTemplate elementincluded in the enhanced video transport session element can have avalue of http://bc/ev-segUri-$TOI$.mp4, a Rep_ID attribute included inthe enhanced video transport session element can have a value of“RepresentationID-ev” and a CP attribute included in the enhanced videotransport session element can indicate “EntityMode”.

A tsi attribute included in an enhanced audio transport session elementcan have a value of “tsi-ea”, a FileTemplate element included in theenhanced audio transport session element can have a value ofhttp://bc/ea-segUri-$TOI$.mp4, a Rep_ID attribute included in theenhanced audio transport session element can have a value of“RepresentationID-ea” and a CP attribute included in the enhanced audiotransport session element can indicate “EntityMode”.

A description will be given of base LSID C720400.

For example, a tsi attribute included in a base video transport sessionelement can have a value of “tsi-v”, a FileTemplate element included inthe base video transport session element can have a value ofhttp://bc/v-segUri-$TOI$.mp4, a Rep_ID attribute included in the basevideo transport session element can have a value of “RepresentationID-v”and a CP attribute included in the base video transport session elementcan indicate “EntityMode”.

A tsi attribute included in a base audio transport session element canhave a value of “tsi-ra”, a FileTemplate element included in the baseaudio transport session element can have a value ofhttp://bc/ra-segUri-$TOI$.mp4, a Rep_ID attribute included in the baseaudio transport session element can have a value of“RepresentationID-ra” and a CP attribute included in the enhanced audiotransport session element can indicate “EntityMode”.

A tsi attribute included in an SSC transport session element may have avalue of “tsi-s”. An EFDT element may include a File element. The Fileelement may include a Content-Location attribute and a TOI attribute.For example, the Content-Location attribute can have a value of“usdUri”. The TOI attribute can have a value of “toi-s-bundl”. A CPattribute included in the SSC transport session element can have a valueof “FileMode(Meta).

FIG. 73 illustrates service layer signaling according to the thirteenthembodiment of the present invention.

Service layer signaling according to the thirteenth embodiment of thepresent invention can provide a method for reducing SDP redundancy.

An SSC C730100 may include USD C730110, an enhanced video SDP C730131, abase video SDP C730133, a base audio SDP C730135 and/or an SSC SDPC730137.

The USD C730110 may include a serviced attribute. For example, theserviceID attribute can have a value of “GUSI-1”.

In addition, the USD C730110 may include path information for theenhanced video SDP C730131, the base video SDP C730133, the base audioSDP C730135 and/or the SSC SDP C730137.

Each of the enhanced video SDP C730131, the base video SDP C730133, thebase audio SDP C730135 and the SSC SDP C730137 may include componentinformation (s), an originator and session identifier (o), a sourcefilter (a), connection information (c), media description (m), an ATSCmode (a, atsc-mode) and/or TSI information (a, route-tsi or flute-tsi).

A description will be given of LSID 730300.

The LSID C730300 may include an enhanced video transport sessionelement, a base video transport session element, a base audio transportsession element and/or an SSC transport session element. The contents ofthe LSID C730300 can include the contents of the aforementioned LSDI.

An SSC C730200 according to the thirteenth embodiment of the presentinvention may include USD C730210 and/or an SDP C730230. The SSC C730200can reduce redundancy by including a single SDP C730230, compared to theSSC C730100.

For example, the SDP C730230 can include component information (s), anoriginator and session identifier (o), a source filter (a), connectioninformation (c), media description (m), an ATSC mode (a, atsc-mode)and/or TSI information (a, route-tsi or flute-tsi).

The SDP C730230 may include an ATSC mode (a=atsc-mode:BCStreamID1,BBPSID3) and/or TSI information (a=route-tsi: (tsi-ev)) foran enhanced video component. In addition, the SDP C730230 may include anATSC mode (a=atsc-mode: BCStreamID1,BBPSID2) and/or TSI information(a=route-tsi: (tsi-v)) for a base video component. Furthermore, the SDPC730230 may include an ATSC mode (a=atsc-mode: BCStreamID1,BBPSID1)and/or TSI information (a=route-tsi: (tsi-a), (tsi-se), (tsi-0)) for anSSC component.

An SSC C730400 according to the thirteenth embodiment of the presentinvention can further reduce redundancy by including an SDP modifiedfrom the SDP C730230. The modified SDP may include only bootstrappinginformation of a ROUTE session. The broadcast reception apparatus canfurther reduce SDP redundancy by discovering a transport session ID(tsi) list, which is described per transport DP, in LSID and matchingthe tsi list to data pipes.

For example, the modified SDP can include media description(m=application destUDPPort1 ROUTE/UDP 0), connection information (c=INIP4 destIPAddr1), a source filter (a=source-filter: incl IN IP4sourceIDAddr1) and/or an ATSC mode (a=atsc-mode: (DP_ID1).

FIG. 74 illustrates a signaling structure for signaling capabilities ofa receiver for using broadcast services/content according to anembodiment of the present invention.

According to an embodiment of the present invention, USD may includeCapabilityDescription. Capability information which is signaled bysignaling information may include essential capability informationindicating capabilities that need to be essentially described to rendera specific broadcast service or broadcast content (broadcastservice/content). While the capability information is non-essential forbroadcast service/content rendering, a receiver having supportablecapability may include information about normal capability for enablingexecution of a specific function. That is, the capability informationcan be classified into essential capability information and normalcapability information.

Unless the capability information is classified into essentialcapability information and normal capability information, the broadcastreceiver can receive and render specific broadcast services/content butthe receiver may skip the broadcast service/content. To solve thisproblem, the present invention can additionally signal essential_flaginformation, which indicates whether corresponding capabilityinformation is essential capability information, for capability_codeinformation.

Referring to FIG. 74(a), USD according to an embodiment of the presentinvention may include @protocolVersion information, @atscServiceIdinformation, @fullMpdUri information, a CapabilityDescription element, acapability_code element, @essential_flag information, aTargetingDescription element, a ContentAdvisoryDescription element, aProgramTitleDescription element, a name element, @lang information, aserviceLanguage element, a requiredCapabilities element and/or a featureelement.

The @protocolVersion information indicates the protocol version of theUSD.

The @atscServiceId information identifies a broadcast service.

The @fullMpdUri information indicates the URI of the location to whichfull MPD is provided.

The CapabilityDescription element may include information whichspecifies capability required for a receiver for meaningful presentationof broadcast services/content.

The capability_code element may include information indicatingcapability required for the receiver to enable meaningful presentationof broadcast services/content. The capability_code element may includeinformation specifying capability type and/or information indicatingstandards of required capability per capability.

The @essential_flag information indicates whether specific capability isessential for broadcast service/content rendering. The @essential_flaginformation may correspond to information indicating whether capabilityspecified by the capability_code element corresponds to essentialcapability information or normal capability information. The@essential_flag information may indicate whether capability informationcorresponds to essential capability information about capabilityessentially necessary to render a broadcast service or broadcast contentor normal capability information about capability which is not essentialfor rending the broadcast service or broadcast content but is necessaryto process a specific element included in the broadcast service orbroadcast content.

The TargetingDescription element may include data and/or informationabout a target to which broadcast services will be provided.

The ContentAdvisoryDescription element may include data and/orinformation for conditional access.

The ProgramTitleDescription may include information indicating the titleof a broadcast program.

The name element may indicate the name of a service, provided by the@lang information. The name element may include the @lang informationindicating the language of the service name. The language may bespecified according to XML data type.

The serviceLanguage element includes information specifying a languagein which a broadcast service is provided.

The requiredCapabilities element may include information indicatingreceiver capability required for a specific service.

The feature element may include information specifying a specificservice included in broadcast services.

Referring to FIG. 74(b), a capability code specifies capability thatsupports HD (High Definition) and the essential_flag with respect to thecapability code is set to “true”. Accordingly, the receiver needs tohave HD processing capability in order to render a correspondingbroadcast service/content. However, when a capability code specifiescapability supporting HDR (High Dynamic Range) and the essential_flagwith respect to the capability code is set to “false”, the receiver canprocess HDR for the corresponding broadcast service/content when thereceiver supports HDR capability.

When a capability code specifies capability that supports UHD (UltraHigh Definition) and the essential_flag with respect to the capabilitycode is set to “true”, the receiver needs to have capability to processUHD in order to render the corresponding broadcast service/content.

According to the present invention, the receiver can control the qualityand property of a broadcast service/content provided thereto inconsideration of device capability and capability information accordingto CapabilityDescription upon reception of signaling information.

When the essential_flag is not present, a receiver having capabilitylower than capability indicated by capability information cannot receivea corresponding broadcast service/content or has to skip the broadcastservice/content even if the receiver receives the same irrespective ofwhether the capability information is essential capability informationor normal capability information. When the essential_flag is used,however, a receiver which has no capability indicated by normalcapability information but has capability indicated by essentialcapability information can receive and render a corresponding broadcastservice/content.

FIG. 75 illustrates a procedure by which a receiver accesses a broadcastservice/content using a signaling structure according to an embodimentof the present invention.

The receiver acquires an FIC (or SLT) from a broadcast signal. Dataspecified by a specific IP address and UDP number may correspond to theFIC in the broadcast signal, and the receiver may acquire the FIC byobtaining the data provided with the IP address and UDP number. Thereceiver may acquire minimum capability information(min_capability_profile information) required for the receiver for abroadcast service specified by serviceID information. The minimumcapability information may specify minimum capability of the receiver,which is necessary to decode one or more broadcast services belonging tothe range of the FIC. In the present embodiment, HD processingcapability corresponds to the minimum capability required for thereceiver.

The receiver may recognize a session or location at which service levelsignaling information (service layer signaling information or a servicesignaling channel) is transmitted using information included in the FIC.The receiver may recognize that data delivered through a transportsession identified by specific TSI information and/or TOI informationcorrespond to service level signaling information.

The receiver acquires MPD using @fullMpdUri information contained in USDincluded in the service level signaling information. The receiverpresents the corresponding broadcast service/content using informationincluded in the MPD.

The receiver may acquire an SDP using information included in the USD.

The receiver acquires a CapabilityDescription element in the USDincluded in the service level signaling information. The receiver may beaware that capability for rendering the broadcast service/contentcorresponds to HD or UHD and capability indicated by normal capabilityinformation for the corresponding broadcast service/content correspondsto HDR processing capability using information contained in theCapabilityDescription element.

The receiver may access a transport session delivering data provided forcorresponding specifications according to whether to process thebroadcast service/content as HD service/content or UHD service/content.The receiver may access a transport session delivering specific datausing information such as LSID.

In the present embodiment, when RepresentationId is “ev”, this indicatesa component for UHD. When RepresentationId is “v”, this indicates acomponent for HD.

FIG. 76 illustrates USD which provides information about a transportsession in which data of a broadcast service/content is transmittedaccording to an embodiment of the present invention.

Referring to FIG. 76(a), when information contained in a deliveryMethodelement of the USD indicates transmission of a component of thebroadcast service/content using the ROUTE protocol of ATSC broadcast,information about location at which LSID including information foraccessing a ROUTE session is transmitted may be additionally included inthe USD.

According to the present invention, a unified signaling method can beused for a broadcast system since information necessary for a receiverto acquire a component can be signaled through information of the USD.In addition, when the value of atsc-mode, which is an attribute added tothe SDP, is defined, the present invention can indicate the attributevalue of atsc-mode using a corresponding broadcast stream id onlyalthough the attribute value should be set by combining the broadcaststream id and the corresponding DP_ID in conventional schemes.

Referring to FIG. 76(a), the USD may include the deliveryMethod element,an r7:unicastAccessURI element, a basePattern element, anr8:alternativeAccessDelivery element, a unicastAccessURI element,timeShiftBuffer attribute information, an r12: broadcastAppServiceelement, @serviceArea information, r12:unicastAppservice element, anatscBroadcastAppService element, @DP_ID information, @BroadcastStreamIDinformation, @IPAddr information, @UDPPort information, @TSIinformation, an atscSdpURI element and/or @LSID_DP_ID information inaddition to the information and/or elements included in theaforementioned USD.

The deliveryMethod element may include data and/or information about amethod for delivering broadcast services.

The r7:unicastAccessURI element may include URI information foraccessing a broadcast service transmitted through a broadband network.

The basePattern element may include the aforementioned base URIinformation. The basePattern element may be a character pattern used bya receiver to be matched to all parts of a segmented URL used by a DASHclient to request media segmentation of parent representation in acorresponding period. Matching refers to delivery of the requested mediasegmentation through broadcast transport. The basePattern element mayindicate a base pattern used to recognize the location of a specificservice in a method of transmitting the specific service according totransport mode.

The r8:alternativeAccessDelivery element includes data and/orinformation about an alternative method for delivering a broadcastservice.

The unicastAccessURI element includes information indicating the URI ofthe location to which a broadcast service delivered by the alternativemethod is provided when the broadcast service is transmitted through abroadband network.

The timeShiftBuffer attribute information includes information aboutdata and/or information about a buffer for time shifting.

The r12:broadcastAppService element includes data and/or informationabout a service delivered through a broadcast network.

The serviceArea element may include information specifying an area towhich a service is provided or the type of the service.

The r12:unicastAppService element may include data and/or informationabout a service delivered through a broadband network.

The atscBroadcastAppService element includes information and/or anelement about a service delivered through the broadcast network.

The @DP_ID information identifies a data pipe delivering a service.

The @BroadcastStreamID information identifies a broadcast stream (orbroadcasting station) delivering a service.

The @IPAddr information indicates the IP address of the location towhich a service is provided.

The @UDPPort information indicates the UDP number of the location towhich data included in a service is transmitted.

The @TSI information identifies a transport session through which dataincluded in a service is transmitted.

The atscSdpURI element may include information which identifies a URIindicating the location to which an ATSC SDP is provided.

The @LSID_DP_ID information identifies a data pipe including LSID.

Referring to FIG. 76(b), the receiver may acquire an SDP or LSID from adata pipe indicated by the @LSID_DP_ID information included in the USD.

FIG. 77 illustrates a procedure by which a receiver accesses a broadcastservice/content using a signaling structure according to an embodimentof the present invention.

The receiver acquires an FIC (or SLT) from a broadcast signal. Dataspecified by a specific IP address and UDP number may correspond to theFIC in the broadcast signal, and the receiver may acquire the FIC byobtaining the data.

The receiver may recognize a session or location at which service levelsignaling information (service layer signaling information or a servicesignaling channel) is transmitted using information included in the FIC.The receiver may recognize that data delivered through a transportsession identified by specific TSI information and/or TOI informationcorresponds to service level signaling information.

The receiver acquires MPD using @fullMpdUri information contained in USDincluded in the service level signaling information. The receiverpresents the corresponding broadcast service/content using informationincluded in the MPD.

The receiver may acquire an SDP using information included in the USD.The USD may include the @LSID_DP_ID information, as described above, andthe receiver may acquire LSID by obtaining data transmitted through adata pipe identified by the @LSID_DP_ID information.

The receiver may access a transport session through which a componentincluded in the corresponding broadcast service/content is transmittedusing information contained in the LSID to acquire related data.

FIG. 78 is a flowchart illustrating a method for generating andprocessing a broadcast signal according to an embodiment of the presentinvention.

A transmitter encodes broadcast data for one or more broadcast services(JS78010).

The transmitter encodes first level signaling information includinginformation which describes properties of the one or more broadcastservices (JS78020).

The transmitter encodes second level signaling information includinginformation for scanning the one or more broadcast services (JS78030).

The transmitter generates a broadcast signal including the first levelsignaling information and the second level signaling information(JS78040).

According to an embodiment of the present invention, the first levelsignaling information may include USD information which describesservice layer properties with respect to the broadcast services.

According to an embodiment of the present invention, the USD informationmay include capability information specifying capabilities necessary topresent broadcast content of the broadcast services.

FIG. 79 is a block diagram illustrating a broadcast system according toan embodiment of the present invention.

The broadcast system according to an embodiment of the present inventionmay include a broadcast transmitter J79100 and/or a broadcast receiverJ790200.

The broadcast transmitter J79100 may include a broadcast data encoderJ79110, a signaling encoder J79120 and/or a broadcast signal generatorJ79130.

The broadcast receiver J790200 may include a broadcast signal receiverJ79210, a processor J79220 and/or a display J79230.

The broadcast data encoder J79110 encodes broadcast data for one or morebroadcast services.

The signaling encoder J79120 encodes first level signaling informationincluding information which describes properties of the one or morebroadcast services and second level signaling information includinginformation for scanning the one or more broadcast services.

The broadcast signal generator J79130 generates a broadcast signalincluding the broadcast data, the first level signaling information andthe second level signaling information.

According to an embodiment of the present invention, the first levelsignaling information may include USD information which describesservice layer properties with respect to the broadcast services.

According to an embodiment of the present invention, the USD informationmay include capability information specifying capabilities necessary topresent broadcast content of the broadcast services.

The broadcast signal receiver J79210 receives the broadcast signalincluding the broadcast data for the one or more broadcast services, thefirst level signaling information including information which describesproperties of the one or more broadcast services and the second levelsignaling information including information for scanning the one or morebroadcast services. The first level signaling information may includeUSD information which describes service layer properties with respect tothe broadcast services and the USD information may include capabilityinformation specifying capabilities necessary to present broadcastcontent of the broadcast services.

The processor J79220 controls the broadcast receiver J79200 to presentthe broadcast services by acquiring the broadcast services using thesecond level signaling information and/or the first level signalinginformation. The processor J79220 may control the broadcast receiverJ79200 to skip the corresponding broadcast services/content whencapabilities of the broadcast receiver are lower than capabilitiesindicated by capability information.

The display J79230 displays the broadcast services/content.

FIG. 80 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention.

The USBD or USD may include URI information for referring to MPD whichis a fragment of SLS, as described above. There are various types of MPDas described above. Full MPD may be MPD including reproduction relatedinformation about all service components included in a correspondingservice. eMBMS MPD may be MPD including reproduction related informationabout a service component delivered by an eMBMS bearer. AppService MPDmay be MPD including reproduction related information about broadcast orunicast service components of mobile broadcasting. As described above,the eMBMS MPD or AppService MPD can be used for genuine mobile broadcastnetwork services.

The full MPD can be used for genuine normal broadcast network servicesand hybrid services (ATSC/3GPP) as described above. The USBD or USD caninclude information referring to various types of MPD, and it ispossible to propose methods of including URI information referring tothe full MPD in the USBD/USD by extending/modifying the USBD/USD.

Here, the USBD or USD may be extended/modified on the basis of one ofUSBDs/USDs according to the aforementioned embodiments. That is, theUSBD/USD extended in the present embodiment may have one of thestructures and fields of the USBDs/USDs according to the aforementionedembodiments.

The illustrated embodiment t80010 of USBD may further include URIinformation for indicating the full MPD. The illustrated embodimentt80010 of the USBD may include @fullMpdUri field. The @fullMpdUri fieldis a lower filed of the USBD/USD element and may describe the URI of thefull MPD to be used in a service in the present embodiment. The@fullMpdUri field may be located under other elements according toembodiments. The @fullMpdUri field may be added to another type ofUSBD/USD to extend the corresponding USBD/USD. The @fullMpdUri field maybe identical to the aforementioned @atsc:fullMPDUri field and@fullMpdUri information.

Other fields included in the illustrated embodiment t80010 of the USBDmay be identical to the aforementioned corresponding ones. For example,name, @lang, serviceLanguage, requiredCapability, feature,deliveryMethod, r7unicastAccessURI, basePattern,r8:alternativeAccessDelivery, unicastAccessURI, timeShiftingBuffer,r12:broadcastAppService, serviceArea and/or r12:unicastAppService shownin the figure can be identical to the aforementioned corresponding ones.

The illustrated diagram t80020 shows a process of referring to MPDsaccording to the present embodiment. The full MPD can be indicated bythe @fullMpdUri field added to the USBD. r9:MPD can be indicated byinformation contained in r9:mediaPresentationDescription of the USBD.r12:MPD can be indicated by information included in r12:appService ofthe USBD. Here, r9:MPD may correspond to the aforementioned eMBMS MPDand r12:MPD may correspond to the aforementioned AppSvc MPD.

It is possible to clearly discriminate the full MPD from other MPDswhile maintaining the structures and syntaxes of previously usedUSBDs/USDs through the aforementioned extension/modification.

FIG. 81 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention.

To refer to the full MPD, r9:mediaPresentationDescription informationincluded in conventional USBD/USD and profile information in MPD may becombined and used.

The r9: mediaPresentationDescription information may include informationrelated to MPD used in conventional mobile broadcasting (e.g. 3GPP).mpdUri information under the r9: mediaPresentationDescription mayinclude URI information of the MPD of mobile broadcasting. This MPD maycorrespond to the aforementioned eMBMS MPD or r9:MPD.

In addition, the MPD may include @profiles information. The @profilesinformation may indicate profile information of the MPD. The @profilesinformation can be used to check the type of the corresponding MPD byserving as the profile identifier of the MPD. This profile informationcan indicate one of MPD profiles defined in DASH. In addition, the MPDmay further include @id information for identifying the MPD.

The present invention can discriminate the full MPD from other MPDs bycombining the r9:mediaPresentationDescription information and theprofile information of MPD. Specifically, the MPD can be referred to bythe mpdUri information in the r9:mediaPresentationDescription. Whetherthe corresponding MPD is full MPD or a different type of MPD can beindicated by the profile information of the referred MPD. For example,the corresponding MPD may be full MPD or r9:MPD according to the profileinformation. As described above, normal broadcast services and hybridservices can use the full MPD and mobile broadcast services can user9:MPD and eMBMS MPD according to embodiments.

In the illustrated USBD/USD t81010, other fields may be identical to theaforementioned corresponding ones, and information other thanr9:mediaPresentationDescription may be extended and the aforementionedoperation may be performed. In addition, the type of corresponding MPDmay be indicated using ID information instead of the profile informationof the MPD.

In the illustrated diagram t81020, MPD is referred to by mpdUriinformation of r9:mediaPresentationDescription. Whether thecorresponding MPD is full MPD can be indicated by the profile attributeof the MPD. Here, one MPD can be used in normal broadcast services(ATSC) as full MPD and another MPD can be used in mobile broadcastservices (3GPP) as eMBMS MPD. r12:MPD may be referred to by informationincluded in r12:appService of the USBD/USD. According to an embodiment,full MPD may be referred to using profile information of MPD referred toby r12:MPD.

It is possible to clearly discriminate the full MPD from other MPDswhile maintaining the structures and syntaxes of previously usedUSBDs/USDs through the aforementioned extension/modification.

FIG. 82 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention.

To refer to full MPD, the USBD/USD can be extended by includinginformation related to the full MPD in the r12:appService element in theconventional USBD/USD.

The r12:appService element may include information related to MPD usedin conventional mobile broadcasting (e.g. 3GPP). The USBD/USD mayfurther include URI information for referring to the full MPD as lowerinformation of the r12:appService element. The URI information may beincluded in @fullMpdUri field. The @fullMpdUri field has been describedabove. Accordingly, information of the r12:appService element can beused to refer to r12:MPD and the @fullMpdUri field added to ther12:appService element can be used to refer to the full MPD. r12:MPD maycorrespond to the aforementioned AppSvc MPD.

In the illustrated USBD/USD t82010, other fields are identical to theaforementioned corresponding fields, and the @fullMpdUri field may beadded to information other than the r12:appService element according toan embodiment.

In the illustrated diagram t82020, the full MPD is referred to by the@fullMpdUri field of the r12:appService element. In addition, r12:MPD isreferred to by the information of the r12:Service element and r9:MPD isreferred to by mpdUri information of r9:mediaPresentationDescription.

It is possible to clearly discriminate the full MPD from other MPDswhile maintaining the structures and syntaxes of previously usedUSBDs/USDs through the aforementioned extension/modification.

FIG. 83 illustrates extended USBD/USD for indicating a full MPD URIaccording to an embodiment of the present invention.

To refer to the full MPD, a separate element may be added to theconventional USBD/USD. The element may include information related tothe full MPD. The full MPD can be referred to using information of theelement.

An atsc:appService element can be added to the aforementioned USBD/USD.This element may include information related to normal broadcastservices and may further include URI information for referring to thefull MPD. @appServiceDescriptionURI field of the atsc:appService elementmay include information referring to the full MPD. The full MPD can bereferred to using this information.

In addition, the atsc:appService element may further includeidenticalContent, basePattern, alternativeContent and/or @mimeTypefields. These fields have been described above and may includeinformation about normal broadcast services described by the addedatsc:appService element.

In the illustrated USBD/USD t83010, other fields have been describedabove. The atsc:appService element may be added to location differentfrom the aforementioned one in the USBD/USD.

In the illustrated diagram t83020, the full MPD is referred to by the@appServiceDescriptionURI field of the added atsc:appService element. Inaddition, r:9MPD is referred to using reference information included inr9:mediaPresentationDescription and r12:MPD is referred to usinginformation of the r12:appService element.

It is possible to clearly discriminate the full MPD from other MPDswhile maintaining the structures and syntaxes of previously usedUSBDs/USDs through the aforementioned extension/modification.

FIG. 84 illustrates a method for transmitting a broadcast signalaccording to an embodiment of the present invention.

The method for transmitting a broadcast signal according to anembodiment of the present invention may include the steps of generatingservice components, service signaling information and a service listtable, encapsulating the service components, the service signalinginformation and the service list table into transport packets,generating link layer packets by link-processing the transport packets,and generating a broadcast signal by physical-layer-processing the linklayer packets and transmitting the broadcast signal.

Specifically, a first module of a transmitting side may generate servicecomponents of at least one service. The service components may beincluded in each service. A service component may include informationsuch as audio/video information or closed captioning. The first modulemay also generate service signaling information signaling such servicedata. The service signaling information may correspond to theaforementioned SLS. The first module may generate a service list table.The service list table may correspond to the aforementioned SLT. The SLTmay be included in low level signaling (LLS) and delivered, as describedabove. This step may correspond to an upper stack of IP/UDP in theprotocol stack. The first module may be a hardware module associatedwith generation of media data for reproduction as a service provider.

The generated service components, SLS and/or SLT may be encapsulatedinto transport packets. Here, the transport packets may correspond to IPpackets. This step may be performed by a second module of thetransmitting side. The second module may be a hardware module associatedwith generation of IP packets in the UDP/IP layer. The packets includingthe SLS and the service components may be delivered through a ROUTE orMMTP transport session. Specifically, the packets may be transmittedthrough a sub-session of the corresponding transport session, that is,an LCT session of the ROUTE session or an MMTP packet flow of the MMTPsession. Packets delivering the SLT (that is, packets delivering theLLS) may be transmitted through a predetermined transport session. TheSLT may be delivered through a transport session identified by apre-designated IP address and UDP port number.

A third module of the transmitting side is a module managing the linklayer and may perform the aforementioned operations such as headercompression and/or link layer packet encapsulation in the link layer.The third module may generate one or more link layer packets byprocessing the generated transport packets in the link layer.

A fourth module of the transmitting side is a module managing thephysical layer and may physical-layer-process the link layer packets.Physical layer processing can include the aforementioned encoding,interleaving, framing and waveform generation operations. In addition,the fourth module may transmit a broadcast signal generated according tophysical layer processing. The third module of the transmitting side maybe included in the fourth module according to an embodiment. The thirdmodule and the fourth module may be integrated into one module accordingto an embodiment.

In the present embodiment, the aforementioned SLT may includeinformation indicating a transport session through which SLS per serviceis delivered. Here, the information indicating a transport session mayrefer to the aforementioned IP/UDP information as bootstrap informationin the SLT.

In a method for transmitting a broadcast signal according to anotherembodiment of the present invention, the service signaling informationmay include user service bundle description (USBD) and the USBD mayserve as a signaling hub which describes technical information about acorresponding service. As described above, the SLS may include the USBD.

In a method for transmitting a broadcast signal according to anotherembodiment of the present invention, the service signaling informationmay further include media presentation description (MPD) and the USBDmay include URI information referring to the MPD. As described above,the SLS may include the MPD. The USBD includes URI information referringto the MPD. Here, the MPD may be full MPD, r9:MPD or r12:MPD accordingto embodiments. The MPD may be full MPD in the case of normal broadcastservices. In this case, the MPD referred to by the USBD may be full MPD,and the URI information referring to the MPD may refer to URIinformation referring to the full MPD included in the USBD. The USBD mayalso include information referring to r9 MPD and r12 MPD. The MPD mayinclude reproduction related information about service components of thecorresponding service delivered through a broadcast network or abroadband network.

In a method for transmitting a broadcast signal according to anotherembodiment of the present invention, the MPD may be full MPD whichdescribes reproduction related information about all service componentsincluded in the corresponding service. The full MPD has been describedabove and may be used in normal broadcast services and hybrid broadcastservices rather than mobile broadcast services.

In a method for transmitting a broadcast signal according to anotherembodiment of the present invention, the USBD may further includetransmission related information about the service components of thecorresponding service. Here, the transmission related information maycorrespond to the aforementioned deliveryMethod field. As describedabove, the deliveryMethod field may be a container of transmissioninformation about service data which can be accessed through a broadcastnetwork or a broadband network.

The deliveryMethod field may include broadcast information, and thebroadcast information may include transmission related information abouta service component of a service transmitted through the broadcastnetwork. Here, the broadcast information may correspond to thebroadcastAppService and r12:broadcastAppService fields included in thedeliveryMethod field. The broadcast information may include informationabout DASH representation including a service component contained in anormal broadcast service. Here, DASH representation may be a servicecomponent delivered through the broadcast network. This field maycorrespond to the aforementioned r12:AppService field according to anembodiment. This field may further include the basePattern field.

In a method for transmitting a broadcast signal according to anotherembodiment of the present invention, the transmission relatedinformation may include unicast information, and the unicast informationmay include transmission related information about a service componentof a service delivered through a broadband network. Here, the unicastinformation may correspond to the unicastAppService andr12:unicastAppService fields included in the deliveryMethod field. Theunicast information may include information about DASH representationincluding a service component contained in a normal broadcast service.Here, DASH representation may be a service component delivered throughthe broadband network. This field may correspond to the aforementionedr12:AppService field according to an embodiment. This field may furtherinclude the basePattern field.

In a method for transmitting a broadcast signal according to anotherembodiment of the present invention, the service signaling informationmay further include transport session description, and the USBD mayfurther include URI information referring to the transport sessiondescription. Here, the transport session description may correspond tothe aforementioned S-TSID. The transport session description maycorrespond to the aforementioned LSID according to an embodiment. Thetransport session description may include session identifier informationidentifying sub-sessions of a transport session through which servicecomponents of a corresponding service are delivered. The transportsession may correspond to a ROUTE or MMTP session and a sub-session maycorrespond to an LCT sessions or an MMTP packet flow. The sessionidentifier information may correspond to TSI information or an MMTPpacket ID.

A description will be given of a method for receiving a broadcast signalaccording to an embodiment of the present invention, which is not shownin the drawings.

The method for receiving a broadcast signal according to an embodimentof the present invention may include the steps of receiving andphysical-layer-processing a broadcast signal by a first module of areceiving side, deencapsulating/decompressing link layer packetsacquired according to physical layer processing into transport packetsby a second module of the receiving side, acquiring an SLT, SLS andservice data by a third module of the receiving module through a reverseprocess of IP/UDP processing and/or providing a service using theacquired service data by a fourth module of the receiving side. Here,physical layer processing, link processing and IP/UDP layer processingof the receiving side may correspond to reverse processes of those ofthe transmitting side. The step of acquiring the service data may besubdivided into bootstrapping of the SLT into SLS and a process ofacquiring service components using information of the SLS, as describedabove. Details have been described above.

Methods for receiving a broadcast signal according to embodiments of thepresent invention may correspond to the methods for transmitting abroadcast signal according to the aforementioned embodiments of thepresent invention. The methods for receiving a broadcast signal may beperformed by hardware modules corresponding to the modules (e.g. thefirst, second, third and fourth modules of the transmitting side) usedin the methods for transmitting a broadcast signal. The methods forreceiving a broadcast signal may have embodiments corresponding to theaforementioned embodiments of the methods for transmitting a broadcastsignal.

The aforementioned steps may be omitted or replaced by steps ofperforming similar/identical operations according to an embodiment.

FIG. 85 illustrates an apparatus for transmitting a broadcast signalaccording to an embodiment of the present invention.

The apparatus for transmitting a broadcast signal according to anembodiment of the present invention may include the aforementionedfirst, second, third and/or fourth modules of the transmitting side. Theblocks and modules have been described above.

The apparatus for transmitting a broadcast signal and internalmodules/blocks thereof according to an embodiment of the presentinvention may perform the methods for transmitting a broadcast signalaccording to the aforementioned embodiments of the present invention.

A description will be given of an apparatus for receiving a broadcastsignal according to an embodiment of the present invention, which is notshown in the drawings.

The apparatus for receiving a broadcast signal according to anembodiment of the present invention may include the aforementionedfirst, second, third and/or fourth modules of the receiving side. Theblocks and modules have been described above.

The apparatus for receiving a broadcast signal and internalmodules/blocks thereof according to an embodiment of the presentinvention may perform the methods for receiving a broadcast signalaccording to the aforementioned embodiments of the present invention.

The internal blocks/modules of the aforementioned apparatuses may beprocessors which perform consecutive processes stored in a memory andmay be hardware elements located inside/outside of the apparatusesaccording to an embodiment.

The aforementioned modules may be omitted or replaced by other modulesperforming similar/identical operations according to embodiments.

Modules or units may be processors executing consecutive processesstored in a memory (or a storage unit). The steps described in theaforementioned embodiments can be performed by hardware/processors.Modules/blocks/units described in the above embodiments can operate ashardware/processors. The methods proposed by the present invention canbe executed as code. Such code can be written on a processor-readablestorage medium and thus can be read by a processor provided by anapparatus.

While the embodiments have been described with reference to respectivedrawings for convenience, embodiments may be combined to implement a newembodiment. In addition, designing a computer-readable recording mediumstoring programs for implementing the aforementioned embodiments iswithin the scope of the present invention.

The apparatus and method according to the present invention are notlimited to the configurations and methods of the above-describedembodiments and all or some of the embodiments may be selectivelycombined to obtain various modifications.

The methods proposed by the present invention may be implemented asprocessor-readable code stored in a processor-readable recording mediumincluded in a network device. The processor-readable recording mediumincludes all kinds of recording media storing data readable by aprocessor. Examples of the processor-readable recording medium include aROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical datastorage device and the like, and implementation as carrier waves such astransmission over the Internet. In addition, the processor-readablerecording medium may be distributed to computer systems connectedthrough a network, stored and executed as code readable in a distributedmanner.

Although the preferred embodiments of the present invention have beendisclosed for illustrative purposes, those skilled in the art willappreciate that various modifications, additions and substitutions arepossible, without departing from the scope and spirit of the inventionas disclosed in the accompanying claims. Such modifications should notbe individually understood from the technical spirit or prospect of thepresent invention.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applied to each other.

Those skilled in the art will appreciate that the present invention maybe carried out in other specific ways than those set forth hereinwithout departing from the spirit and essential characteristics of thepresent invention. Therefore, the scope of the invention should bedetermined by the appended claims and their legal equivalents, not bythe above description, and all changes coming within the meaning andequivalency range of the appended claims are intended to be embracedtherein.

In the specification, both the apparatus invention and the methodinvention are mentioned and description of both the apparatus inventionand the method invention can be applied complementarily.

Various embodiments have been described in the best mode for carryingout the invention.

The present invention is applied to broadcast signal providing fields.

Various equivalent modifications are possible within the spirit andscope of the present invention, as those skilled in the relevant artwill recognize and appreciate. Accordingly, it is intended that thepresent invention cover the modifications and variations of thisinvention provided they come within the scope of the appended claims andtheir equivalents.

What is claimed is:
 1. An apparatus for receiving a broadcast signal,comprising: a tuner configured to receive a broadcast signal, thebroadcast signal including service components of a broadcast service,service signaling information signaling the broadcast service and aservice list table including information for bootstrapping the servicesignaling information; a hardware processor configured to parse thebroadcast signal and obtain the service list table, the servicesignaling information and the service components of the broadcastservice, wherein the service signaling information includes firstsession description data and second session description data, whereinthe first session description data includes IP/UDP informationidentifying a Real-Time Object Delivery over Unidirectional Transport(ROUTE) session in the broadcast signal, and the second sessiondescription data for the identified ROUTE session includes TransportSession Identifiers (TSIs) for identifying Layered Coding Transport(LCT) channels that carry the service components delivered through theidentified ROUTE session; and a display configured to display thebroadcast service using the service components.
 2. The apparatus ofclaim 1, wherein the broadcast signal further includes a mapping tablehaving information identifying a Physical Layer Pipe (PLP) through whichthe service components are delivered.
 3. The apparatus of claim 1,wherein the information for bootstrapping the service signalinginformation is used to identify a ROUTE session carrying the servicesignaling information.
 4. The apparatus of claim 1, wherein the servicesignaling information further includes a User Service Bundle Description(USBD) and a Media Presentation Description (MPD).
 5. The apparatus ofclaim 4, wherein the USBD serves as a signaling hub describing technicalinformation about the broadcast service, and wherein the MPD includesinformation about media representation of the service components.
 6. Amethod of receiving a broadcast signal, comprising: receiving, by atuner, a broadcast signal, the broadcast signal including servicecomponents of a broadcast service, service signaling informationsignaling the broadcast service and a service list table includinginformation for bootstrapping the service signaling information;parsing, by a hardware processor, the broadcast signal; obtaining, bythe hardware processor, the service list table, the service signalinginformation and the service components of the broadcast service, whereinthe service signaling information includes first session descriptiondata and second session description data, wherein the first sessiondescription data includes IP/UDP information identifying a Real-TimeObject Delivery over Unidirectional Transport (ROUTE) session in thebroadcast signal, and the second session description data for theidentified ROUTE session includes Transport Session Identifiers (TSIs)for identifying Layered Coding Transport (LCT) channels that carry theservice components delivered through the identified ROUTE session; anddisplaying, by a display, the broadcast service using the servicecomponents.
 7. The method of claim 6, wherein the broadcast signalfurther includes a mapping table having information identifying aPhysical Layer Pipe (PLP) through which the service components aredelivered.
 8. The method of claim 6, wherein the information forbootstrapping the service signaling information is used to identify aROUTE session carrying the service signaling information.
 9. The methodof claim 6, wherein the service signaling information further includes aUser Service Bundle Description (USBD) and a Media PresentationDescription (MPD).
 10. The method of claim 9, wherein the USBD serves asa signaling hub describing technical information about the broadcastservice, and wherein the MPD includes information about mediarepresentation of the service components.